From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xin Li <xin3.li@intel.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [RFC PATCH 1/1] x86/traps: Get rid of exception handlers' second argument error code
Date: Fri, 4 Aug 2023 12:35:23 +0200 [thread overview]
Message-ID: <f3c20dd0-9914-f646-0aaa-400dffd2bb2b@suse.com> (raw)
In-Reply-To: <f0077c58-9192-9c81-6c2d-df845bfb7815@citrix.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 626 bytes --]
On 04.08.23 12:25, Andrew Cooper wrote:
> On 04/08/2023 8:57 am, Xin Li wrote:
>> I haven't checked Xen implications with this change, i.e., does Xen
>> hypervisor need to adjust how it passes arguments to PV guests?
>
> This is an internal detail of how Linux handles data on it's stacks,
> isn't it?
>
> The Xen code in Linux will need adjustment to match, but this is not a
> hypervisor ABI (which obviously can't and won't change).
The only adaption of Xen code will need to happen for the only use of
DEFINE_IDTENTRY_RAW_ERRORCODE() there, and this you have covered in your
patch already.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-08-04 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 7:57 Xin Li
2023-08-04 10:13 ` Peter Zijlstra
2023-08-04 17:35 ` Li, Xin3
2023-08-04 19:01 ` Peter Zijlstra
2023-08-05 21:02 ` Thomas Gleixner
2023-08-04 10:25 ` Andrew Cooper
2023-08-04 10:35 ` Juergen Gross [this message]
2023-08-04 17:20 ` Li, Xin3
2023-08-04 17:19 ` Li, Xin3
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=f3c20dd0-9914-f646-0aaa-400dffd2bb2b@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xin3.li@intel.com \
/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
all inboxes | Powered by JetHome®