From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: PVH questions
Date: Mon, 28 Jan 2013 18:42:03 -0800 [thread overview]
Message-ID: <20130128184203.4efb96ea@mantra.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301281330250.10432@kaball.uk.xensource.com>
On Mon, 28 Jan 2013 15:09:57 +0000
Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 28 Jan 2013, Samuel Thibault wrote:
> > Hello,
> >
> > I've had a look at PVH support, and I have a few questions:
> >
> > - events are still dispatched the PV way through the callback,
> > right?
>
> No, they are injected as an X86 vector (0xf3).
>
>
> > - I guess FPU errors don't trigger an INT13, so I don't need to
> > handle that?
>
> I think that's right, but Mukesh can confirm this.
>
>
> > - How about the console and store MFNs from the boot info? Are they
> > still MFNs, or actually PFNs?
>
> PFNs
>
>
> > - How about PV network in non-copy mode? It used to be done
> > with a page transfer, which the frontend would free, does
> > XENMEM_decrease_reservation still use MFNs, or PFNs?
>
> PFNs
>
> Mukesh, did I get it right?
Yes.
> Would you be up for writing down these basic pieces of information
> regarding the PVH interface on a wiki page?
> So that other kernel hackers like Samuel can port their favourite open
> source kernel to it?
> Maybe add something about the shared_info page and the grant_table
> too.
Sure. Lets collect questions and I'll do that after my version 2 patch
is out.
thaks,
mukesh
next prev parent reply other threads:[~2013-01-29 2:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 1:59 PVH questions Samuel Thibault
2013-01-28 2:00 ` Samuel Thibault
2013-01-30 14:00 ` Samuel Thibault
2013-01-30 14:28 ` Stefano Stabellini
2013-01-30 14:58 ` Samuel Thibault
2013-01-30 16:08 ` Stefano Stabellini
2013-01-30 16:19 ` Samuel Thibault
2013-01-30 16:22 ` Samuel Thibault
2013-01-28 15:09 ` Stefano Stabellini
2013-01-28 16:06 ` Konrad Rzeszutek Wilk
2013-01-28 16:20 ` Jan Beulich
2013-01-28 16:31 ` Stefano Stabellini
2013-01-28 16:17 ` Samuel Thibault
2013-01-29 2:42 ` Mukesh Rathor [this message]
2013-01-31 1:02 ` Samuel Thibault
2013-01-31 1:06 ` Samuel Thibault
2013-01-31 11:51 ` Stefano Stabellini
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=20130128184203.4efb96ea@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).