From: "Roger Pau Monné" <roger.pau@citrix.com>
To: samuel.thibault@ens-lyon.org,
George Dunlap <george.dunlap@eu.citrix.com>,
tech mailinglists <mailinglists.tech@gmail.com>,
xen-users@lists.xen.org, xen-devel <xen-devel@lists.xen.org>
Subject: Re: Questions about PVH in Xen 4.3 unstable
Date: Wed, 30 Jan 2013 12:43:28 +0000 [thread overview]
Message-ID: <51091570.6050802@citrix.com> (raw)
In-Reply-To: <20130130123255.GV6193@type.bordeaux.inria.fr>
On 30/01/13 12:32, Samuel Thibault wrote:
> Samuel Thibault, le Wed 30 Jan 2013 13:26:08 +0100, a écrit :
>> Samuel Thibault, le Wed 30 Jan 2013 13:20:16 +0100, a écrit :
>>> Roger Pau Monné, le Wed 30 Jan 2013 11:11:00 +0000, a écrit :
>>>> On 30/01/13 11:04, George Dunlap wrote:
>>>>> Yes, PVH is an extension of PV; so only operating systems which can be
>>>>> ported to PV will support PVH.
>>>>
>>>> Isn't it probably easier to port a system with PVHVM support to PVH?
>>>
>>> In general, no. Porting a system to PV involves a lot of tricky things
>>> deep in the OS, while writing a PV driver is much less involving.
>>
>> Let me fix it: porting a system to PVH involves a lot less tricky things
>> deep in the OS than porting it to PV. There are still quite a few tricky
>> things to do, so I don't think PVH is half-way between PV and PVHVM.
>
> Let me fix it again :)
>
> Starting from PV, most of what you need to support PVH is to just drop
> the PV implementation and use the native code, without writing any code.
>From what I saw, PVH uses most of the PVHVM code paths, like the PVHVM
vector callback for events (not the PV callback), and grant frames are
also using the PVHVM paths, so I was thinking that the transition from
PVHVM to PVH was going to be easier than the transition from PV to PVH.
But yes, you also need some of the PV tricks, so I'm not sure what will
be more difficult to implement, the PV tricks or the PVHVM infrastructure.
Anyway, it is surely going to be much more easier to port a OS to PVH
from scratch compared to PV.
> So even if it PVH was actually halfway between PVHVM and PV, it surely
> is not halfway between PV and PVHVM :)
>
> Samuel
>
next prev parent reply other threads:[~2013-01-30 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 10:33 Questions about PVH in Xen 4.3 unstable tech mailinglists
2013-01-30 10:47 ` Samuel Thibault
2013-01-30 10:52 ` tech mailinglists
2013-01-30 10:56 ` Samuel Thibault
2013-01-30 11:04 ` George Dunlap
2013-01-30 11:11 ` Roger Pau Monné
2013-01-30 12:20 ` Samuel Thibault
2013-01-30 12:26 ` Ian Campbell
2013-01-30 12:33 ` Samuel Thibault
2013-01-30 12:26 ` Samuel Thibault
2013-01-30 12:32 ` Samuel Thibault
2013-01-30 12:43 ` Roger Pau Monné [this message]
2013-01-30 13:35 ` tech mailinglists
2013-01-30 15:02 ` Samuel Thibault
2013-01-30 11:29 ` Jan Beulich
2013-01-30 12:04 ` tech mailinglists
2013-01-30 12:22 ` Samuel Thibault
2013-01-30 12:25 ` George Dunlap
2013-01-30 12:19 ` Samuel Thibault
2013-01-30 10:50 ` George Dunlap
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=51091570.6050802@citrix.com \
--to=roger.pau@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=mailinglists.tech@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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 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.