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: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	KonradRzeszutek Wilk <konrad.wilk@oracle.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Is: PVH + ARM new hypercalls. Was: Re: [PATCH]: PVH: specify xen features strings cleany for PVH
Date: Thu, 31 Jan 2013 18:23:29 -0800	[thread overview]
Message-ID: <20130131182329.2cb3a225@mantra.us.oracle.com> (raw)
In-Reply-To: <5107B6FC02000078000BA589@nat28.tlf.novell.com>

On Tue, 29 Jan 2013 10:48:12 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 29.01.13 at 03:57, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > On xen side I added the ifdef:
> > 
> > #if __XEN_INTERFACE_VERSION__ < 0x00040300
> >     unsigned long gdt_frames[16], gdt_ents; /* GDT (machine frames,
> > # ents) */
> > #else
> >     union {
> >         struct {
> >             /* GDT (machine frames, # ents) */
> >             unsigned long gdt_frames[16], gdt_ents;
> >         } pv;
> >         struct {
> >             /* PVH: GDTR addr and size */
> >             unsigned long gdtaddr, gdtsz;
> >         } pvh;
> >     } u;
> > #endif
> > 
> > but it doesn't matter on linux side, so up to you.
> 
> But I'd still prefer for this to go away again - you could simply use
> gdt_frames[0] for gdtaddr and gdt_ents for the (normalized)
> gdtsz.

That was my patch version 1 during linux patch review. Then the reviewer
suggested to make it a union.

> And if you nevertheless go the union route, call it "gdt" instead
> of "u" and drop the gdt/gdt_ prefixes from the member names
> (yes, I know, grepping and cscoping for such member is more
> difficult, but I continue to see more advantage in avoiding the
> redundancy).

That was my patch version 2, where I called it gdt and another reviewer
suggested to change to u. So I changed it to u.

It's gone thru enough iterations that I'd like to leave as is. Thank
you in advance for your compromise in helping us mortals grep/cscope 
to learn code.

Thanks,
Mukesh

  reply	other threads:[~2013-02-01  2:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19  1:35 [PATCH]: PVH: specify xen features strings cleany for PVH Mukesh Rathor
2013-01-21 12:06 ` Jan Beulich
2013-01-22 23:12   ` Mukesh Rathor
2013-01-23  8:22     ` Jan Beulich
2013-01-23 22:43       ` Mukesh Rathor
2013-01-24  9:16         ` Jan Beulich
2013-01-24  9:27           ` Ian Campbell
2013-01-24 15:10             ` Konrad Rzeszutek Wilk
2013-01-24 23:13           ` Mukesh Rathor
2013-01-25  8:02             ` Jan Beulich
2013-01-25 10:11               ` Ian Campbell
2013-01-25 10:27                 ` Jan Beulich
2013-01-25 10:43                   ` Ian Campbell
2013-01-28 16:26                     ` Is: PVH + ARM new hypercalls. Was: " Konrad Rzeszutek Wilk
2013-01-29  2:57                       ` Mukesh Rathor
2013-01-29 10:48                         ` Jan Beulich
2013-02-01  2:23                           ` Mukesh Rathor [this message]
2013-02-01 16:24                             ` Jan Beulich
2013-02-01 19:27                               ` Mukesh Rathor
2013-02-04 10:31                                 ` Ian Campbell
2013-02-05  1:04                                   ` Mukesh Rathor
2013-02-05  7:53                                     ` Jan Beulich

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=20130131182329.2cb3a225@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@kernel.org \
    --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).