public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] ignore AMDs HWCR register access to set the FFDIS bit
Date: Wed, 24 Jun 2009 12:58:28 +0300	[thread overview]
Message-ID: <4A41F8C4.6080102@redhat.com> (raw)
In-Reply-To: <1245709224-974-1-git-send-email-andre.przywara@amd.com>

On 06/23/2009 01:20 AM, Andre Przywara wrote:
> Linux tries to disable the flush filter on all AMD K8 CPUs. Since KVM
> does not handle the needed MSR, the injected #GP will panic the Linux
> kernel. Ignore setting of the HWCR.FFDIS bit in this MSR to let Linux
> boot with an AMD K8 family guest CPU.
>
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
> ---
>   arch/x86/kvm/x86.c |    7 +++++++
>   1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 5a66bb9..4c19c24 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -796,6 +796,13 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, u32 msr, u64 data)
>   	case MSR_EFER:
>   		set_efer(vcpu, data);
>   		break;
> +	case MSR_K7_HWCR:
> +		if (data != 0x40) {
> +			pr_unimpl(vcpu, "unimplemented HWCR wrmsr: 0x%llx\n",
> +				data);
> +			return 1;
> +		}
> +		break;
>    

Won't that printk() if writing a zero?  Just mask out that bit.

I also see some HWCR handling in svm.c, can probably be removed.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-06-24  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 22:20 [PATCH 1/2] ignore AMDs HWCR register access to set the FFDIS bit Andre Przywara
2009-06-24  9:58 ` Avi Kivity [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=4A41F8C4.6080102@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=kvm@vger.kernel.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