xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH 10/16]: PVH xen: introduce vmx_pvh.c
Date: Thu, 21 Feb 2013 20:33:43 +0000	[thread overview]
Message-ID: <20130221203343.GA32191@ocelot.phlegethon.org> (raw)
In-Reply-To: <20130221112004.05fdb740@mantra.us.oracle.com>

At 11:20 -0800 on 21 Feb (1361445604), Mukesh Rathor wrote:
> > It still needs to be handled. :)   You are testing this stuff on AMD
> > as well, right?
> 
> Right, in pvh_svm.c when its ported. I had talked to someone from AMD
> at xen summit who said he'd port it to AMD as soon as phase I patch
> is checked in. It shouldn't be too hard to do that. I estimate a week
> or two if I was to do SVM changes. 

OK, so long as there's a plan. :)

Cheers,

Tim.

      reply	other threads:[~2013-02-21 20:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  2:01 [RFC PATCH 10/16]: PVH xen: introduce vmx_pvh.c Mukesh Rathor
2013-01-14 11:59 ` Jan Beulich
2013-01-15  0:54   ` Mukesh Rathor
2013-01-15  8:46     ` Jan Beulich
2013-01-24  1:59       ` Mukesh Rathor
2013-01-24  9:21         ` Jan Beulich
2013-01-25  2:29           ` Mukesh Rathor
2013-01-24 16:31 ` Tim Deegan
2013-01-25  2:15   ` Mukesh Rathor
2013-01-25  2:18   ` Mukesh Rathor
2013-02-20  0:05   ` Mukesh Rathor
2013-02-20  9:58     ` Tim Deegan
2013-02-21  3:05       ` Mukesh Rathor
2013-02-21  9:10         ` Tim Deegan
2013-02-21 19:20           ` Mukesh Rathor
2013-02-21 20:33             ` Tim Deegan [this message]

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=20130221203343.GA32191@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=Xen-devel@lists.xensource.com \
    --cc=mukesh.rathor@oracle.com \
    /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).