From: Joao Martins <joao.m.martins@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH] xen/x86: Adjust stack pointer in xen_sysexit
Date: Tue, 17 Nov 2015 10:53:58 +0000 [thread overview]
Message-ID: <564B0746.8090505@oracle.com> (raw)
In-Reply-To: <CALCETrXExPZyAtkc8pR1qr0ugweRGuuPOPw=_wju5V0=wswPmg@mail.gmail.com>
On 11/16/2015 09:04 PM, Andy Lutomirski wrote:
> On Mon, Nov 16, 2015 at 1:03 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>> On Mon, Nov 16, 2015 at 12:50:19PM -0800, Andy Lutomirski wrote:
>>> On Mon, Nov 16, 2015 at 12:48 PM, Boris Ostrovsky
>>> <boris.ostrovsky@oracle.com> wrote:
>>>> On 11/16/2015 03:22 PM, Borislav Petkov wrote:
>>>>>
>>>>> On Mon, Nov 16, 2015 at 12:11:11PM -0800, Andy Lutomirski wrote:
>>>>>
>>>>>> Are there really multiple feature bits for this stuff? I'd like to
>>>>>> imagine that the entry code is all either Xen PV or native/PVH/PVHVM
>>>>>> -- i.e. I assumed that PVH works like native for all entries.
>>>>
>>>>
>>>>
>>>> Almost. For PVH we will have a small stub to set up bootparams and such but
>>>> then we jump to startup_{32|64} code.
>>>>
>>>>
>>>>> I just reacted to Boris' statement:
>>>>>
>>>>> "We don't currently have a Xen-specific CPU feature. We could, in
>>>>> principle, add it but we can't replace all of current paravirt patching
>>>>> with a single feature since PVH guests use a subset of existing pv ops
>>>>> (and in the future it may become even more fine-grained)."
>>>>
>>>>
>>>> Actually, nevermind this --- I was thinking about APIC ops and they are not
>>>> pv ops.
>>>>
>>>> Note though that there are other users of pv ops --- lguest and looks like
>>>> KVM (for one op) use them too.
>>>>
>>>
>>> Honestly, I think we should just delete lguest some time soon. And
>>> KVM uses this stuff so lightly that we shouldn't need all of the pvop
>>> stuff. (In fact, I'm slowly working on removing KVM_GUEST's
>>> dependency on PARAVIRT.)
>>
>> Even for the pvclock?
>>
>> (sorry for stealing this thread on this subject).
>
> I don't think that pvclock uses any of the paravirt infrastructure.
> It's just another clock source AFAIK.
>
Yeah, but pv_time_ops is still used on both Xen and KVM. Even though it looks
that on KVM some of it's used only when pvclock isn't marked as stable (i.e. no
PVCLOCK_TSC_STABLE_BIT).
Joao
> --Andy
>
next prev parent reply other threads:[~2015-11-17 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 23:18 [PATCH] xen/x86: Adjust stack pointer in xen_sysexit Boris Ostrovsky
2015-11-13 23:26 ` Andy Lutomirski
2015-11-14 1:23 ` Boris Ostrovsky
2015-11-15 18:02 ` Andy Lutomirski
2015-11-16 16:25 ` Boris Ostrovsky
2015-11-16 19:03 ` Andy Lutomirski
2015-11-16 19:59 ` Borislav Petkov
2015-11-16 20:11 ` Andy Lutomirski
2015-11-16 20:22 ` Borislav Petkov
2015-11-16 20:48 ` Boris Ostrovsky
2015-11-16 20:50 ` Andy Lutomirski
2015-11-16 21:00 ` Borislav Petkov
[not found] ` <20151116210314.GA10307@char.us.oracle.com>
2015-11-16 21:04 ` Andy Lutomirski
2015-11-17 10:53 ` Joao Martins [this message]
2015-11-16 21:55 ` H. Peter Anvin
2015-11-17 14:40 ` Boris Ostrovsky
2015-11-17 18:49 ` Andy Lutomirski
2015-11-17 19:12 ` [Xen-devel] " Andrew Cooper
2015-11-17 19:16 ` Andy Lutomirski
2015-11-17 19:21 ` Borislav Petkov
2015-11-17 19:29 ` Andrew Cooper
2015-11-17 19:36 ` Andy Lutomirski
2015-11-17 19:37 ` Boris Ostrovsky
2015-11-17 19:38 ` Boris Ostrovsky
2015-11-16 20:31 ` Boris Ostrovsky
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=564B0746.8090505@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=xen-devel@lists.xen.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