kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/5] qemu-kvm: msix: Only invoke msix_handle_mask_update on changes
Date: Tue, 18 Oct 2011 15:52:39 +0200	[thread overview]
Message-ID: <4E9D84A7.3000609@siemens.com> (raw)
In-Reply-To: <20111018134921.GA4946@redhat.com>

On 2011-10-18 15:49, Michael S. Tsirkin wrote:
> On Tue, Oct 18, 2011 at 03:20:43PM +0200, Michael S. Tsirkin wrote:
>> Ah. Right. Good catch. It's probably best to just make that
>> state be !enabled || masked. Like the below? (compiled only):
>>
>> --->
>>
>> msix: track function masked in pci device state
>>
>> Only go over the table when function is masked.
>> This optimization is not really important for qemu.git but helps
>> qemu-kvm.git.
>>
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> 
> ...
> 
>> diff --git a/hw/pci.h b/hw/pci.h
>> index 86a81c8..da4c9c3 100644
>> --- a/hw/pci.h
>> +++ b/hw/pci.h
>> @@ -178,6 +178,8 @@ struct PCIDevice {
>>      unsigned *msix_entry_used;
>>      /* Region including the MSI-X table */
>>      uint32_t msix_bar_size;
>> +    /* MSIX function mask set or MSIX disabled */
>> +    bool msix_function_masked;
>>      /* Version id needed for VMState */
>>      int32_t version_id;
> 
> BTW, since code checks msix_function_masked consistently,
> this also covers the case your other patch addressed,
> where there's a table access while msix is disabled, right?

Looks like. Not sure about potential side effects of this change to
msi_is_masked, but conceptually there should be none.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-10-18 13:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  7:50 [PATCH 0/5] qemu-kvm: MSI-X fixes Jan Kiszka
2011-10-18  7:50 ` [PATCH 1/5] qemu-kvm: msix: Don't fire notifier spuriously on set/unset Jan Kiszka
2011-10-18 11:06   ` Michael S. Tsirkin
2011-10-18 11:34     ` Jan Kiszka
2011-10-18  7:50 ` [PATCH 2/5] qemu-kvm: msix: Only invoke msix_handle_mask_update on changes Jan Kiszka
2011-10-18 11:43   ` Michael S. Tsirkin
2011-10-18 11:54     ` Jan Kiszka
2011-10-18 12:11       ` Michael S. Tsirkin
2011-10-18 12:22         ` Jan Kiszka
2011-10-18 12:37           ` Michael S. Tsirkin
2011-10-18 12:44             ` Jan Kiszka
2011-10-18 13:20               ` Michael S. Tsirkin
2011-10-18 13:49                 ` Michael S. Tsirkin
2011-10-18 13:52                   ` Jan Kiszka [this message]
2011-10-18  7:50 ` [PATCH 3/5] qemu-kvm: msix: Fire mask notifier on global mask changes Jan Kiszka
2011-10-18  7:50 ` [PATCH 4/5] msix: Don't process table changes while disabled Jan Kiszka
2011-10-18 11:18   ` Michael S. Tsirkin
2011-10-18 11:35     ` Jan Kiszka
2011-10-18 12:01       ` Michael S. Tsirkin
2011-10-18 11:26   ` Michael S. Tsirkin
2011-10-18  7:50 ` [PATCH 5/5] msix: Prevent bogus mask updates on MMIO accesses 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=4E9D84A7.3000609@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.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;
as well as URLs for NNTP newsgroup(s).