From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 211467] Regression affecting 32->64 bit SYSENTER on AMD
Date: Mon, 01 Feb 2021 10:31:57 +0000 [thread overview]
Message-ID: <bug-211467-28872-D4GyC4pvy9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211467-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211467
jonny5532 (jonny@magicstring.co.uk) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #294993|0 |1
is obsolete| |
--- Comment #3 from jonny5532 (jonny@magicstring.co.uk) ---
Created attachment 295027
--> https://bugzilla.kernel.org/attachment.cgi?id=295027&action=edit
Patch with whitespace fix and SOB
Thanks for confirming, here's the same patch again without the missing newline
and with my SOB tacked on the bottom. I am indeed not set up for sending
patches so would appreciate it if you could do that bit.
I had a look through emulate.c to see if I could foresee any unintended side
effects - it seems that SYSEXIT already handles the potential transition back
from 64->32 bits.
I do note that some of the transitions to PROT64 are wrapped in "#ifdef
CONFIG_X86_64 ... #endif", for example in em_syscall. However that looks pretty
dubious in itself - if em_syscall gets run with the guest in long mode, on a 32
bit kernel, then it'll just fail to update the EIP but carry on regardless.
Probably an unlikely scenario however (KVM on AMD has only ever worked on 64
bit procs as I understand).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-02-01 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 20:50 [Bug 211467] New: Regression affecting 32->64 bit SYSENTER on AMD bugzilla-daemon
2021-01-29 21:47 ` [Bug 211467] " bugzilla-daemon
2021-01-29 23:38 ` bugzilla-daemon
2021-02-01 10:31 ` bugzilla-daemon [this message]
2021-02-01 21:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-211467-28872-D4GyC4pvy9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox