public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/7] qemu-kvm: Rename kvm_msix_message to KVMMsiMessage
Date: Wed, 27 Apr 2011 17:40:56 +0300	[thread overview]
Message-ID: <4DB82AF8.3030305@redhat.com> (raw)
In-Reply-To: <4DB828A3.5050804@siemens.com>

On 04/27/2011 05:30 PM, Jan Kiszka wrote:
> On 2011-04-27 16:29, Avi Kivity wrote:
> >  On 04/27/2011 05:04 PM, Jan Kiszka wrote:
> >>>
> >>>   I put kvm_msix_message in pci.h to avoid having every pci device pull in kvm.h
> >>>   is anything wrong with that?  Maybe just rename it to make it generic
> >>>   for msi and leave if where it is.
> >>
> >>  kvm.h shall provide kvm related types, not some unrelated header. That's
> >>  even more important with MSI support for non-PCI devices (aka HPET).
> >
> >  We could have an MSIMessage type that abstracts the general facility,
> >  and let it embed a KVMMsiMessage that contains just the gsi.
>
> Yes, likely also useful for generic MSI delivery services that bypass
> stl_phys.
>

Right, so you can cache the phys_page and apic lookups.

A different layer in which to accomplish this is to have a per-device 
tlb.  So we'd have

     CachedPhysicalAddress msi_fsb_tlb;

     stl_phys_tlb(&msi_fsb_cache, addr, data);

which caches the addr lookup in a 1-entry tlb.  If we have many non-msi 
repeated device writes to the same address, this might be worthwhile.  
 From a quick look at the code, I don't think we do, though.

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


  reply	other threads:[~2011-04-27 14:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 10:23 [PATCH 0/7] qemu-kvm: Clean up and enhance MSI irqchip support Jan Kiszka
2011-04-23 10:23 ` [PATCH 1/7] qemu-kvm: Drop unneeded kvm_irq_routing_entry declaration Jan Kiszka
2011-04-23 10:23 ` [PATCH 2/7] qemu-kvm: Rename kvm_msix_message to KVMMsiMessage Jan Kiszka
2011-04-27 13:34   ` Michael S. Tsirkin
2011-04-27 14:04     ` Jan Kiszka
2011-04-27 14:29       ` Avi Kivity
2011-04-27 14:30         ` Jan Kiszka
2011-04-27 14:40           ` Avi Kivity [this message]
2011-04-27 14:47             ` Jan Kiszka
2011-04-27 14:36         ` Michael S. Tsirkin
2011-04-27 14:35       ` Michael S. Tsirkin
2011-04-23 10:23 ` [PATCH 3/7] qemu-kvm: Refactor MSI core API of KVM Jan Kiszka
2011-04-23 10:23 ` [PATCH 4/7] qemu-kvm: Fix and clean up msix vector use/unuse hooks Jan Kiszka
2011-04-27 12:06   ` Michael S. Tsirkin
2011-04-23 10:23 ` [PATCH 5/7] qemu-kvm: Move gsi bits from kvm_msix_vector_add to kvm_msi_add_message Jan Kiszka
2011-04-27 12:54   ` Michael S. Tsirkin
2011-04-27 13:29     ` Jan Kiszka
2011-04-27 13:36       ` Michael S. Tsirkin
2011-04-23 10:23 ` [PATCH 6/7] qemu-kvm: Move entry comparison into kvm_msi_update_message Jan Kiszka
2011-04-23 10:23 ` [PATCH 7/7] qemu-kvm: Add in-kernel irqchip support for MSI Jan Kiszka
2011-04-27 13:31   ` Michael S. Tsirkin
2011-04-27 14: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=4DB82AF8.3030305@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox