Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

qemu: expose RDTSCP to guests #100645

Closed
wants to merge 1 commit into from
Closed

qemu: expose RDTSCP to guests #100645

wants to merge 1 commit into from

Conversation

moio
Copy link
Contributor

@moio moio commented May 2, 2022

馃憢 Homebrew maintainers!

This is my first time contribution, I hope I did it right, apologies in advance if I didn't!

This is to fix a QEMU bug where the RDTSCP instruction, while available on the host, will not be exposed in the guest. Patch is taken from the QEMU mailing list - it has been recently proposed but it is not in master yet.

Original issue: https://gitlab.com/qemu-project/qemu/-/issues/1011

Issues indirectly caused: rancher-sandbox/rancher-desktop#1324, m3db/m3#3105 m3db/m3#3659 m3db/m3#3827


  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

@Bo98
Copy link
Member

Bo98 commented May 2, 2022

Patch seems alright to me, it seems like it's something Apple themselves have noticed, which boosts my confidence in it. Though I wonder if there's anything we can do to get some sort of movement on it upstream given it was submitted several months ago.

@SMillerDev
Copy link
Member

I'm not sure we'd want to merge a patch that has not been accepted upstream yet but I'll leave it open for other maintainers to chime in.

@fxcoudert
Copy link
Member

If it's not been accepted/merged upstream, not sure we want it.

@github-actions
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale No recent activity label May 23, 2022
@moio
Copy link
Contributor Author

moio commented May 24, 2022

I am waiting for the patch to be accepted in upstream qemu

@github-actions github-actions bot removed the stale No recent activity label May 24, 2022
@github-actions
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale No recent activity label Jun 15, 2022
@moio
Copy link
Contributor Author

moio commented Jun 15, 2022

Upstream contributor apparently still wants to have the patch merged. I will ping this PR as soon as that happens.

@github-actions github-actions bot removed the stale No recent activity label Jun 15, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jul 6, 2022

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale No recent activity label Jul 6, 2022
@moio
Copy link
Contributor Author

moio commented Jul 13, 2022

Patch is under review upstream now https://patchew.org/QEMU/20220712221607.9933-1-f4bug@amsat.org/

@github-actions github-actions bot removed the stale No recent activity label Jul 13, 2022
@BrewTestBot BrewTestBot added the automerge-skip `brew pr-automerge` will skip this pull request label Jul 13, 2022
@moio
Copy link
Contributor Author

moio commented Jul 14, 2022

Patch was accepted upstream.

https://gitlab.com/qemu-project/qemu/-/commit/d8cf2c29cc1077cd8f8ab0580b285bff92f09d1c

Are there any remaining concerns to merge this?

@SMillerDev
Copy link
Member

It should use the upstream commit in the formula.

Adds a patch to resolve
https://gitlab.com/qemu-project/qemu/-/issues/1011

Signed-off-by: Silvio Moioli <silvio@moioli.net>
@BrewTestBot BrewTestBot removed the automerge-skip `brew pr-automerge` will skip this pull request label Jul 18, 2022
@moio
Copy link
Contributor Author

moio commented Jul 18, 2022

It should use the upstream commit in the formula.

Addressed, and rebased for good measure.

@BrewTestBot
Copy link
Member

馃 A scheduled task has triggered a merge.

@github-actions github-actions bot added the outdated PR was locked due to age label Aug 18, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants