All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	peterx@redhat.com, Andrew Jones <drjones@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: GET_SUPPORTED_CPUID and irqchip (was Re: kvm_pv_unhalt and kernel_irqchip=off)
Date: Mon, 15 Aug 2016 20:32:37 +0200	[thread overview]
Message-ID: <20160815183236.GC12385@potion> (raw)
In-Reply-To: <20160815180023.GR5627@thinpad.lan.raisama.net>

2016-08-15 15:00-0300, Eduardo Habkost:
> On Mon, Aug 15, 2016 at 07:50:59PM +0200, Radim Krčmář wrote:
> [...]
>> +static void kvm_clear_invalid_cpuid(struct kvm_vcpu *vcpu)
>> +{
>> +	struct kvm *kvm = vcpu->kvm;
>> +	struct kvm_cpuid_entry2 *best;
>> +
>> +	if (!kvm->clear_invalid_cpuid)
>> +		return;
>> +
>> +	best = kvm_find_cpuid_entry(vcpu, 1, 0);
>> +	if (best && !lapic_in_kernel(vcpu))
>> +		best->ecx &= ~F(X2APIC);
> 
> Isn't it possible to implement x2apic support in userspace APIC
> using the current KVM interfaces?

No, MSR accesses never get to userspace.  We'll probably implement it in
the future as there already has been a proposal for unhandled MSRs.

      reply	other threads:[~2016-08-15 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 18:27 kvm_pv_unhalt and kernel_irqchip=off Eduardo Habkost
2016-08-10 19:04 ` Radim Krčmář
2016-08-10 20:58   ` Radim Krčmář
2016-08-12 18:37   ` GET_SUPPORTED_CPUID and irqchip (was Re: kvm_pv_unhalt and kernel_irqchip=off) Eduardo Habkost
2016-08-13 12:43     ` Radim Krčmář
2016-08-15 13:03       ` Eduardo Habkost
2016-08-15 13:21         ` Paolo Bonzini
2016-08-15 17:50         ` Radim Krčmář
2016-08-15 18:00           ` Eduardo Habkost
2016-08-15 18:32             ` Radim Krčmář [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=20160815183236.GC12385@potion \
    --to=rkrcmar@redhat.com \
    --cc=drjones@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.