From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>,
Eddie Dong <eddie.dong@intel.com>,
Jacob Shin <jacob.shin@amd.com>,
xen-devel <xen-devel@lists.xen.org>,
Jun Nakajima <jun.nakajima@intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/HVM: key handler registration functions can be __init
Date: Wed, 10 Jul 2013 14:38:30 -0500 [thread overview]
Message-ID: <51DDB836.7050209@amd.com> (raw)
In-Reply-To: <CE0305BC.57BC0%keir.xen@gmail.com>
On 7/10/2013 6:36 AM, Keir Fraser wrote:
> On 10/07/2013 11:38, "Jan Beulich" <JBeulich@suse.com> wrote:
>
>> This applies to both SVM and VMX.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Keir Fraser <keir@xen.org>
Acked-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>
>> --- a/xen/arch/x86/hvm/svm/vmcb.c
>> +++ b/xen/arch/x86/hvm/svm/vmcb.c
>> @@ -310,7 +310,7 @@ static struct keyhandler vmcb_dump_keyha
>> .desc = "dump AMD-V VMCBs"
>> };
>>
>> -void setup_vmcb_dump(void)
>> +void __init setup_vmcb_dump(void)
>> {
>> register_keyhandler('v', &vmcb_dump_keyhandler);
>> }
>> --- a/xen/arch/x86/hvm/vmx/vmcs.c
>> +++ b/xen/arch/x86/hvm/vmx/vmcs.c
>> @@ -1492,7 +1492,7 @@ static struct keyhandler vmcs_dump_keyha
>> .desc = "dump Intel's VMCS"
>> };
>>
>> -void setup_vmcs_dump(void)
>> +void __init setup_vmcs_dump(void)
>> {
>> register_keyhandler('v', &vmcs_dump_keyhandler);
>> }
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
prev parent reply other threads:[~2013-07-10 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 10:38 [PATCH] x86/HVM: key handler registration functions can be __init Jan Beulich
2013-07-10 11:36 ` Keir Fraser
2013-07-10 19:38 ` Suravee Suthikulpanit [this message]
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=51DDB836.7050209@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=eddie.dong@intel.com \
--cc=jacob.shin@amd.com \
--cc=jun.nakajima@intel.com \
--cc=keir.xen@gmail.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).