From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2 1/3] x86: Export FPU API for KVM use
Date: Mon, 17 May 2010 12:24:47 +0300 [thread overview]
Message-ID: <4BF10B5F.5030300@redhat.com> (raw)
In-Reply-To: <201005171719.23570.sheng@linux.intel.com>
On 05/17/2010 12:19 PM, Sheng Yang wrote:
> On Monday 17 May 2010 17:19:02 Avi Kivity wrote:
>
>> On 05/17/2010 12:08 PM, Sheng Yang wrote:
>>
>>> Also add some constants.
>>>
>>>
>>> +++ b/arch/x86/kernel/process.c
>>> @@ -28,6 +28,7 @@ unsigned long idle_nomwait;
>>>
>>> EXPORT_SYMBOL(idle_nomwait);
>>>
>>> struct kmem_cache *task_xstate_cachep;
>>>
>>> +EXPORT_SYMBOL(task_xstate_cachep);
>>>
>>> int arch_dup_task_struct(struct task_struct *dst, struct task_struct
>>> *src) {
>>>
>> _GPL() unless good reason not to.
>>
> Oops... Just copied and pasted the above line...
>
>
No matter, I'll update it when applying if no further comments
(reviewing 3 now).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-05-17 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 9:08 [PATCH][v2 0/3] Convert KVM to use FPU API Sheng Yang
2010-05-17 9:08 ` [PATCH][v2 1/3] x86: Export FPU API for KVM use Sheng Yang
2010-05-17 9:19 ` Avi Kivity
2010-05-17 9:19 ` Sheng Yang
2010-05-17 9:24 ` Avi Kivity [this message]
2010-05-17 9:22 ` Sheng Yang
2010-05-17 9:08 ` [PATCH][v2 2/3] KVM: x86: Use unlazy_fpu() for host FPU Sheng Yang
2010-05-17 9:08 ` [PATCH][v2 3/3] KVM: x86: Use FPU API Sheng Yang
2010-05-17 9:37 ` Avi Kivity
2010-05-17 9:37 ` [PATCH][v2 0/3] Convert KVM to use " Avi Kivity
2010-05-19 16:17 ` Avi Kivity
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=4BF10B5F.5030300@redhat.com \
--to=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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).