From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Gleb Natapov <gleb@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: assign-dev: Purpose of interrupt_work
Date: Mon, 12 Oct 2009 11:16:54 +0200 [thread overview]
Message-ID: <4AD2F406.9050108@redhat.com> (raw)
In-Reply-To: <4AD2F1D0.4090005@web.de>
On 10/12/2009 11:07 AM, Jan Kiszka wrote:
>> I'm worried about disabling irqs for non-device-assignment cases. It
>> would be more palatable if ioapic was completely O(1) (there are some
>> per-vcpu loops in there, shouldn't be too bad for 16 vcpus, but we want
>> to scale).
>>
> Yeah, what a pity. That's likely not solvable in a generic way, given
> that the guest finally decided how many VCPUs may listen to a line.
>
> OK, but dropping interrupt_work from the MSI path is still worthwhile,
> and probably more future-proof anyway.
>
Yes - we can extend the irq routing table to contain this information.
It means we need to invalidate it when the guest reprograms the
interrupt controllers, but I think it should work out fine.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-12 9:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 7:03 assign-dev: Purpose of interrupt_work Jan Kiszka
2009-10-12 7:13 ` Gleb Natapov
2009-10-12 7:27 ` Jan Kiszka
2009-10-12 7:45 ` Gleb Natapov
2009-10-12 7:50 ` Jan Kiszka
2009-10-12 7:57 ` Gleb Natapov
2009-10-12 8:16 ` Jan Kiszka
2009-10-12 8:39 ` Gleb Natapov
2009-10-12 9:04 ` Jan Kiszka
2009-10-12 9:14 ` Avi Kivity
2009-10-12 9:25 ` Jan Kiszka
2009-10-12 9:30 ` Avi Kivity
2009-10-12 9:38 ` Gleb Natapov
2009-10-12 9:40 ` Avi Kivity
2009-10-12 9:42 ` Gleb Natapov
2009-10-12 9:14 ` Gleb Natapov
2009-10-12 8:39 ` Avi Kivity
2009-10-12 9:05 ` Gleb Natapov
2009-10-12 9:07 ` Avi Kivity
2009-10-12 9:07 ` Jan Kiszka
2009-10-12 9:16 ` Avi Kivity [this message]
2009-10-12 17:36 ` Marcelo Tosatti
2009-10-12 20:44 ` Jan Kiszka
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=4AD2F406.9050108@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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 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.