From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Yang Zhang <yang.zhang.wz@gmail.com>,
"Lan, Tianyu" <tianyu.lan@intel.com>,
pbonzini@redhat.com, kvm@vger.kernel.org, tglx@linutronix.de,
gleb@redhat.com, mst@redhat.com, x86@kernel.org,
Peter Xu <peterx@redhat.com>, Igor Mammedov <imammedo@redhat.com>
Subject: Re: Enable more than 255 VCPU support without irq remapping function in the guest
Date: Thu, 28 Apr 2016 17:32:51 +0200 [thread overview]
Message-ID: <20160428153251.GA17368@potion> (raw)
In-Reply-To: <5721B394.9050008@siemens.com>
2016-04-28 08:54+0200, Jan Kiszka:
> On 2016-04-28 03:11, Yang Zhang wrote:
>> On 2016/4/27 17:45, Jan Kiszka wrote:
>>> On 2016-04-27 11:39, Yang Zhang wrote:
>>>> I mean in Tianyu's case, if he doesn't care about to deliver external
>>>> interrupt to CPU >255, IR is not required.
>>>
>>> What matters is the guest OS. See my other reply on this why this
>>> doesn't work, even for Linux.
>>
>> Since there only few devices in his case, set the irq affinity manually
>> is enough.
You could configure non-IPIs to work, but we want to create options that
are hard to break.
> Ah, wait - are we talking about emulating the Xeon Phi architecture in
> QEMU, accelerated by KVM?
Knights Landing will also be manufactured as a CPU, hopefully without
many peculiarities.
I think we are talking about extending KVM's IR-less x2APIC, when
standard x2APIC is the future.
next prev parent reply other threads:[~2016-04-28 15:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 16:14 Enable more than 255 VCPU support without irq remapping function in the guest Lan, Tianyu
2016-04-26 16:17 ` Jan Kiszka
2016-04-26 16:49 ` Radim Krčmář
2016-04-27 4:10 ` Yang Zhang
2016-04-27 5:24 ` Jan Kiszka
2016-04-27 6:24 ` Lan Tianyu
2016-04-27 6:56 ` Jan Kiszka
2016-04-27 9:39 ` Yang Zhang
2016-04-27 9:45 ` Jan Kiszka
2016-04-28 1:11 ` Yang Zhang
2016-04-28 6:54 ` Jan Kiszka
2016-04-28 15:32 ` Radim Krčmář [this message]
2016-04-29 2:09 ` Yang Zhang
2016-04-29 3:01 ` Nadav Amit
2016-05-03 1:34 ` Yang Zhang
2016-04-29 4:59 ` Jan Kiszka
2016-05-03 1:52 ` Yang Zhang
2016-05-03 2:03 ` Nadav Amit
2016-05-03 4:55 ` Jan Kiszka
2016-05-04 1:46 ` Yang Zhang
2016-05-04 1:56 ` Nadav Amit
2016-05-04 5:38 ` Jan Kiszka
2016-04-27 5:39 ` Lan Tianyu
2016-04-27 14:38 ` Radim Krčmář
2016-04-27 5:15 ` Lan Tianyu
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=20160428153251.GA17368@potion \
--to=rkrcmar@redhat.com \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=tglx@linutronix.de \
--cc=tianyu.lan@intel.com \
--cc=x86@kernel.org \
--cc=yang.zhang.wz@gmail.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.