From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
jun.nakajima@intel.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH RFC V7 4/5] xen, libxc: Request page fault injection via libxc
Date: Wed, 27 Aug 2014 14:54:37 +0300 [thread overview]
Message-ID: <53FDC6FD.4040209@bitdefender.com> (raw)
In-Reply-To: <53FCB226020000780002DA7B@mail.emea.novell.com>
On 08/26/2014 05:13 PM, Jan Beulich wrote:
>>>> On 13.08.14 at 17:28, <rcojocaru@bitdefender.com> wrote:
>> + case XEN_DOMCTL_set_pagefault_info:
>> + {
>> + ret = -EINVAL;
>> +
>> + if ( is_hvm_domain(d) )
>> + {
>> + d->arch.hvm_domain.fault_info.address_space =
>> + op->u.set_pagefault_info.address_space;
>> + d->arch.hvm_domain.fault_info.virtual_address =
>> + op->u.set_pagefault_info.virtual_address;
>> + d->arch.hvm_domain.fault_info.errcode =
>> + op->u.set_pagefault_info.errcode;
>> + d->arch.hvm_domain.fault_info.valid = 1;
>> +
>> + ret = 0;
>> + }
>> + }
>
> Pointless curly braces.
You're right, of course, but I've written it like that because that
seems to be the style (even where it is not necessary / no local
variables are introduced) in
do_domctl(XEN_GUEST_HANDLE_PARAM(xen_domctl_t) u_domctl).
Should I break with the coding style for this switch case?
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2014-08-27 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:28 [PATCH RFC V7 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-08-13 15:28 ` [PATCH RFC V7 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-08-13 15:28 ` [PATCH RFC V7 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-08-26 14:05 ` Jan Beulich
2014-08-13 15:28 ` [PATCH RFC V7 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-08-26 14:13 ` Jan Beulich
2014-08-26 14:24 ` Razvan Cojocaru
2014-08-26 14:44 ` Jan Beulich
2014-08-26 14:56 ` Razvan Cojocaru
2014-08-26 15:49 ` Jan Beulich
2014-08-26 16:59 ` Razvan Cojocaru
2014-08-27 0:54 ` Tian, Kevin
2014-08-27 6:58 ` Jan Beulich
2014-08-28 13:15 ` Tim Deegan
2014-08-28 13:19 ` Razvan Cojocaru
2014-08-27 11:54 ` Razvan Cojocaru [this message]
2014-08-27 12:10 ` Jan Beulich
2014-08-27 12:15 ` Razvan Cojocaru
2014-08-13 15:28 ` [PATCH RFC V7 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-08-26 13:56 ` [PATCH RFC V7 1/5] xen: Emulate with no writes Jan Beulich
2014-08-26 14:01 ` Razvan Cojocaru
2014-08-26 14:19 ` Jan Beulich
2014-08-26 14:30 ` Razvan Cojocaru
2014-08-26 14:40 ` Jan Beulich
2014-08-26 14:45 ` Razvan Cojocaru
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=53FDC6FD.4040209@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.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).