kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tiejun Chen <tiejun.chen@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] xsave: export get_xsave_addr
Date: Fri, 28 Nov 2014 11:29:53 +0100	[thread overview]
Message-ID: <54784EA1.7080106@redhat.com> (raw)
In-Reply-To: <1417166928-6281-1-git-send-email-tiejun.chen@intel.com>



On 28/11/2014 10:28, Tiejun Chen wrote:
> After commit, 1d7fe1d1, "KVM: x86: support XSAVES usage in the host",
> is introduced,
> 
>   ...
>   Building modules, stage 2.
>   MODPOST 20 modules
> ERROR: "get_xsave_addr" [arch/x86/kvm/kvm.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 
> so we need to export get_xsave_addr() while using KVM as
> a module.
> 
> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
> ---
> 
> I'm not sure if this is already fixed so just post in advance.

Yes, it is fixed---Stephen Rothwell's linux-next testing caught it
immediately.  Pushing the XSAVES patch was unintended, since it hadn't
been tested nor reviewed.

Paolo

> 
>  arch/x86/kernel/xsave.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/x86/kernel/xsave.c b/arch/x86/kernel/xsave.c
> index 4c540c4..0de1fae 100644
> --- a/arch/x86/kernel/xsave.c
> +++ b/arch/x86/kernel/xsave.c
> @@ -738,3 +738,4 @@ void *get_xsave_addr(struct xsave_struct *xsave, int xstate)
>  
>  	return (void *)xsave + xstate_comp_offsets[feature];
>  }
> +EXPORT_SYMBOL_GPL(get_xsave_addr);
> 

      reply	other threads:[~2014-11-28 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28  9:28 [PATCH] xsave: export get_xsave_addr Tiejun Chen
2014-11-28 10:29 ` Paolo Bonzini [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=54784EA1.7080106@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=tiejun.chen@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).