xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC PATCH 1/8]: PVH: Basic and preparatory changes
Date: Mon, 20 Aug 2012 16:42:21 -0700	[thread overview]
Message-ID: <20120820164221.3ce8f879@mantra.us.oracle.com> (raw)
In-Reply-To: <1345192554.30865.93.camel@zakaz.uk.xensource.com>

On Fri, 17 Aug 2012 09:35:54 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:

> On Thu, 2012-08-16 at 01:57 +0100, Mukesh Rathor wrote:
> 
> > +void __init xen_arch_setup(void)
> > +{
> > +       xen_panic_handler_init();
> > +
> > +       if (!xen_pvh_domain())
> > +               xen_non_pvh_arch_setup();
> 
> The negative in the fn name here strikes me as a bit weird. Can't this
> just be xen_pv_arch_setup?

Well, PVH is PV, so xen_pv_arch_setup would be confusing. Thus I can't
say if (xen_pv_domain()). The negative logic tells the reader right
away that the PV code doesn't apply to PVH. I earlier had
xen_pure_pv_arch_setup(), but like non_pvh better.

> Or even just have:
> 	/* Everything else is specific to PV without hardware support
> */ if (xen_pvh_domain())
> 		return;

No, the code following if statement is common to both PV and PVH.

  parent reply	other threads:[~2012-08-20 23:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  0:57 [RFC PATCH 1/8]: PVH: Basic and preparatory changes Mukesh Rathor
2012-08-16 13:59 ` Stefano Stabellini
2012-08-16 18:46   ` Mukesh Rathor
2012-08-17  8:28     ` Ian Campbell
2012-08-17 10:56       ` Stefano Stabellini
2012-08-17 13:48         ` Ian Campbell
2012-08-17 19:17         ` Mukesh Rathor
2012-08-17 10:15     ` Stefano Stabellini
2012-08-17 19:20       ` Mukesh Rathor
2012-08-17 19:36         ` Ian Campbell
2012-08-17 19:36         ` Konrad Rzeszutek Wilk
2012-08-17 22:26           ` Mukesh Rathor
2012-08-18  8:56             ` Ian Campbell
2012-08-20 11:02             ` Stefano Stabellini
2012-08-20 17:50               ` Mukesh Rathor
2012-08-17  8:35 ` Ian Campbell
2012-08-17 19:24   ` Mukesh Rathor
2012-08-17 19:47     ` Ian Campbell
2012-08-17 20:05       ` Konrad Rzeszutek Wilk
2012-08-20 23:42   ` Mukesh Rathor [this message]
2012-09-10 13:55 ` Ian Campbell
2012-09-11 21:57   ` Mukesh Rathor
2012-09-12  8:12     ` Ian Campbell
     [not found]       ` <20120912110254.10bde333@mantra.us.oracle.com>
     [not found]         ` <1347474380.25803.21.camel@dagon.hellion.org.uk>
2012-09-12 19:32           ` Mukesh Rathor
2012-09-13  6:00             ` Ian Campbell
2012-09-13 17:14               ` Mukesh Rathor
2012-09-13 17:36                 ` Pasi Kärkkäinen
2012-09-13 18:08                   ` Ian Campbell
2012-09-13 20:45                     ` Konrad Rzeszutek Wilk
2012-09-13 21:09                       ` Ian Campbell

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=20120820164221.3ce8f879@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=konrad.wilk@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).