From: Wei Liu <wei.liu2@citrix.com>
To: PGNet Dev <pgnet.dev@gmail.com>
Cc: roger.pau@citrix.com, wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: Clarifying PVH mode requirements
Date: Mon, 1 Feb 2016 12:29:05 +0000 [thread overview]
Message-ID: <20160201122905.GE10990@citrix.com> (raw)
In-Reply-To: <56AF4E52.30006@gmail.com>
On Mon, Feb 01, 2016 at 04:23:46AM -0800, PGNet Dev wrote:
> On 02/01/2016 01:59 AM, Wei Liu wrote:
> >(Cc Roger)
> >
> >On Sun, Jan 31, 2016 at 01:27:23PM -0800, PGNet Dev wrote:
> >>I run Xen 4.6 Dom0
> >>
> >> rpm -qa | egrep -i "kernel-default-4|xen-4"
> >> kernel-default-devel-4.4.0-8.1.g9f68b90.x86_64
> >> xen-4.6.0_08-405.1.x86_64
> >>
> >>My guests are currently HVM in PVHVM mode; I'm exploring PVH.
> >>
> >>IIUC, for 4.6, this doc
> >>
> >> http://xenbits.xen.org/docs/4.6-testing/misc/pvh-readme.txt
> >>
> >
> >AIUI that document is not very up to date.
> >
> >In the mean time. There is another document in the same directory called
> >pvh.markdown that you can have a look.
>
> There's no
>
> http://xenbits.xen.org/docs/4.6-testing/misc/pvh.markdown
>
> but there is,
>
> (1) http://xenbits.xen.org/docs/unstable/misc/pvh.html
>
> which also looks 'dusty'
>
> This looks more promising,
>
> (2) https://github.com/mirage/xen/blob/master/docs/misc/pvh.markdown
>
I think
(1) http://xenbits.xen.org/docs/unstable/misc/pvh.html
is generate from
(2) https://github.com/mirage/xen/blob/master/docs/misc/pvh.markdown
In any case, yes, I was referring to (2).
Wei.
> That the one?
next prev parent reply other threads:[~2016-02-01 12:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 21:27 Clarifying PVH mode requirements PGNet Dev
2016-02-01 3:47 ` PGNet Dev
2016-02-01 10:30 ` Roger Pau Monné
2016-02-01 12:16 ` PGNet Dev
2016-02-01 9:59 ` Wei Liu
2016-02-01 12:23 ` PGNet Dev
2016-02-01 12:29 ` Wei Liu [this message]
2016-02-01 12:29 ` Roger Pau Monné
2016-02-01 12:38 ` PGNet Dev
2016-02-01 13:38 ` PGNet Dev
2016-02-01 14:54 ` Boris Ostrovsky
2016-02-01 16:56 ` Jan Beulich
2016-02-01 19:17 ` Boris Ostrovsky
2016-02-02 9:32 ` Jan Beulich
2016-02-02 15:51 ` Jan Beulich
2016-02-02 16:16 ` PGNet Dev
2016-02-01 10:28 ` Roger Pau Monné
2016-02-01 12:30 ` PGNet Dev
2016-02-01 14:11 ` Boris Ostrovsky
2016-02-01 15:49 ` PGNet Dev
2016-02-01 19:14 ` Boris Ostrovsky
2016-02-01 19:27 ` PGNet Dev
2016-02-01 19:58 ` Boris Ostrovsky
2016-02-01 23:49 ` Brendan Gregg
2016-02-02 15:28 ` Boris Ostrovsky
2016-02-04 22:01 ` PGNet Dev
2016-02-04 22:39 ` 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=20160201122905.GE10990@citrix.com \
--to=wei.liu2@citrix.com \
--cc=pgnet.dev@gmail.com \
--cc=roger.pau@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 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.