xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 10/16]: PVH xen: introduce vmx_pvh.c
Date: Mon, 14 Jan 2013 16:54:08 -0800	[thread overview]
Message-ID: <20130114165408.0778f73b@mantra.us.oracle.com> (raw)
In-Reply-To: <50F4013202000078000B5421@nat28.tlf.novell.com>

On Mon, 14 Jan 2013 11:59:30 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 12.01.13 at 03:01, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > The heart of this patch is vmx exit handler for PVH guest. It is
> > nicely isolated in a separate module. A call to it is added to
> > vmx_pvh_vmexit_handler().
> 
> I'm sorry to say that, but this patch doesn't look worth commenting
> on in detail: It's completely unsorted (mixing VMX and generic stuff)
> and appears heavily redundant with other code. I think this needs
> to be sorted out cleanly first.

Hi Jan,

Not sure what you are referring to when you generic stuff, but it's 
all VMX stuff, mainly vmx exit handler. We had discussed it during 
the hackathon and the xen summit prior, and we wanted to keep functions
and code for PVH as much separate as possible to avoid filling existing
HVM code with if PVH statements. I can look into moving some stuff to
common code if you have issues with any specific ones? Or do you not
want a separate exit handler for PVH case at all? I think keeping it
separate is much better thing to do.... 

thanks for looking at the patches.
Mukesh

  reply	other threads:[~2013-01-15  0:54 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 [this message]
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

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=20130114165408.0778f73b@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.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).