From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Xiantao Zhang <xiantao.zhang@intel.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/1] IRQ Routing
Date: Wed, 14 Jan 2009 16:31:29 +0200 [thread overview]
Message-ID: <496DF741.9060707@redhat.com> (raw)
In-Reply-To: <200901141639.29844.sheng@linux.intel.com>
Sheng Yang wrote:
> On Wednesday 14 January 2009 04:02:29 Avi Kivity wrote:
>
>> Following is my alternative to irq routing. The differences compared to
>> Sheng's version are:
>>
>> - A single ioctl to replace the entire routing table, instead of add/remove
>> ioctls for individual routing entries. Routing changes are rare, and
>> we need to track the entire table in userspace anyway (for save/restore,
>> and for user irqchip). As a side effect changes are atomic.
>> - Interrupt numbers are allocated by userspace, instead of the kernel
>> - I implemented irqchip routings rather then MSIs, it should be easy to
>> add MSIs later on.
>>
>> Please review and comment.
>>
>
> Look nice to me now... Save/restore is a good reason to maintain a table in
> userspace.
>
> And looking forward to userspace patch. Put a table in kvm_context?
>
Sent out. I indeed placed a table in kvm_context, with add/del route APIs.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-01-14 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 20:02 [PATCH 0/1] IRQ Routing Avi Kivity
2009-01-13 20:02 ` [PATCH 1/1] KVM: Userspace controlled irq routing Avi Kivity
2009-01-14 8:39 ` [PATCH 0/1] IRQ Routing Sheng Yang
2009-01-14 14:31 ` 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=496DF741.9060707@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
--cc=xiantao.zhang@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