From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com, luto@amacapital.net
Subject: Re: [PATCH v1] xen: get rid of paravirt op adjust_exception_frame
Date: Wed, 26 Jul 2017 08:59:08 -0400 [thread overview]
Message-ID: <5978921C.6020605@oracle.com> (raw)
In-Reply-To: <20170724142853.26448-1-jgross@suse.com>
On 7/24/2017 10:28 AM, Juergen Gross wrote:
> When running as Xen pv-guest the exception frame on the stack contains
> %r11 and %rcx additional to the other data pushed by the processor.
>
> Instead of having a paravirt op being called for each exception type
> prepend the Xen specific code to each exception entry. When running as
> Xen pv-guest just use the exception entry with prepended instructions,
> otherwise use the entry without the Xen specific code.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
(I'd s/xen/x86/ in subject to get x86 maintainers' attention ;-))
next prev parent reply other threads:[~2017-07-26 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:28 [PATCH v1] xen: get rid of paravirt op adjust_exception_frame Juergen Gross
2017-07-26 12:59 ` Boris Ostrovsky
2017-07-26 12:59 ` Boris Ostrovsky [this message]
2017-07-26 13:48 ` Andy Lutomirski
2017-07-26 13:48 ` Andy Lutomirski
2017-07-26 14:01 ` Andrew Cooper
2017-07-26 14:01 ` [Xen-devel] " Andrew Cooper
2017-07-26 14:09 ` Andy Lutomirski
2017-07-26 14:31 ` Andrew Cooper
2017-07-26 14:31 ` [Xen-devel] " Andrew Cooper
2017-07-26 14:09 ` Andy Lutomirski
2017-07-26 15:12 ` Juergen Gross
2017-07-26 15:12 ` Juergen Gross
2017-07-26 15:50 ` Juergen Gross
2017-07-26 17:57 ` Andy Lutomirski
2017-07-26 18:43 ` Juergen Gross
2017-07-26 18:43 ` Juergen Gross
2017-07-26 20:15 ` Andy Lutomirski
2017-07-26 20:15 ` Andy Lutomirski
2017-07-26 17:57 ` Andy Lutomirski
2017-07-26 15:50 ` Juergen Gross
-- strict thread matches above, loose matches on Subject: below --
2017-07-24 14:28 Juergen Gross
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=5978921C.6020605@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.