xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH v3 1/4] xen/save: pass a size parameter to the HVM compat functions
Date: Tue, 24 Nov 2015 13:54:23 +0100	[thread overview]
Message-ID: <56545DFF.2040404@citrix.com> (raw)
In-Reply-To: <564F4C3502000078000B7430@prv-mh.provo.novell.com>

El 20/11/15 a les 16.37, Jan Beulich ha escrit:
>>>> On 18.11.15 at 17:37, <roger.pau@citrix.com> wrote:
>> --- a/xen/include/xen/hvm/save.h
>> +++ b/xen/include/xen/hvm/save.h
>> @@ -60,6 +60,8 @@ void _hvm_read_entry(struct hvm_domain_context *h,
>>   */
>>  #define _hvm_load_entry(_x, _h, _dst, _strict) ({                       \
>>      int r;                                                              \
>> +    struct hvm_save_descriptor *d                                       \
>> +        = (struct hvm_save_descriptor *)&(_h)->data[(_h)->cur];         \
> 
> This would seem to belong in the else if() body below. Also I
> don't think "d" is a suitable name for a variable inside a macro
> (albeit the same would apply to "r" too).

Patch #2 makes use of "d" in the first "if" branch also. I don't think
it makes much sense to put it inside of the "else if" branch if I have
to move it in the following patch.

Regarding the name, I don't have a strong opinion, desc is more
descriptive, but it's also longer which means I might have to break some
lines inside of the macro even more.

Roger.

  reply	other threads:[~2015-11-24 12:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 16:37 [PATCH v3 0/4] Introduce a fpu_initilised field to HVM CPU context Roger Pau Monne
2015-11-18 16:37 ` [PATCH v3 1/4] xen/save: pass a size parameter to the HVM compat functions Roger Pau Monne
2015-11-20 14:17   ` Andrew Cooper
2015-11-20 15:37   ` Jan Beulich
2015-11-24 12:54     ` Roger Pau Monné [this message]
2015-11-24 13:06       ` Jan Beulich
2015-11-24 13:11         ` Roger Pau Monné
2015-11-18 16:37 ` [PATCH v3 2/4] xen/save: allow the usage of zeroextend and a fixup function Roger Pau Monne
2015-11-20 14:32   ` Andrew Cooper
2015-11-20 15:41   ` Jan Beulich
2015-11-18 16:37 ` [PATCH v3 3/4] xen/hvm: introduce a fpu_uninitialised field to the CPU save record Roger Pau Monne
2015-11-20 14:35   ` Andrew Cooper
2015-11-20 15:49   ` Jan Beulich
2015-11-24 13:10     ` Roger Pau Monné
2015-11-24 13:34       ` Jan Beulich
2015-11-24 14:38         ` Roger Pau Monné
2015-11-24 14:48           ` Jan Beulich
2015-11-18 16:37 ` [PATCH v3 4/4] Revert "libxc: create an initial FPU state for HVM guests" Roger Pau Monne

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=56545DFF.2040404@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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).