qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: skandasa@cisco.com, etmartin@cisco.com, qemu-devel@nongnu.org,
	wexu2@cisco.com
Subject: [Qemu-devel] Re: [PATCH 6/6] msix: remove range checks.
Date: Wed, 27 Oct 2010 16:52:06 +0200	[thread overview]
Message-ID: <20101027145206.GA4074@redhat.com> (raw)
In-Reply-To: <676a90a3f99920d2d3b9ecec3ac6c83c87cacc12.1288174753.git.yamahata@valinux.co.jp>

On Wed, Oct 27, 2010 at 07:21:21PM +0900, Isaku Yamahata wrote:
> Same as 4b78560503a802eae3663ace9f9cf080319e7265
> > config write handlers should be idempotent.
> > So no need for range checks.
> 
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>

Well I changed my mind on 4b78560503a802eae3663ace9f9cf080319e7265 :) As
long as the check is simple, it does not hurt.

> ---
>  hw/msix.c |    5 -----
>  1 files changed, 0 insertions(+), 5 deletions(-)
> 
> diff --git a/hw/msix.c b/hw/msix.c
> index f66d255..20caa5e 100644
> --- a/hw/msix.c
> +++ b/hw/msix.c
> @@ -157,14 +157,9 @@ static void msix_handle_mask_update(PCIDevice *dev, int vector)
>  void msix_write_config(PCIDevice *dev, uint32_t addr,
>                         uint32_t val, int len)
>  {
> -    unsigned enable_pos = dev->msix_cap + MSIX_CONTROL_OFFSET;
>      int vector;
>      int i;
>  
> -    if (!range_covers_byte(addr, len, enable_pos)) {
> -        return;
> -    }
> -
>      if (!msix_enabled(dev)) {
>          return;
>      }
> -- 
> 1.7.1.1

  reply	other threads:[~2010-10-27 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 10:21 [Qemu-devel] [PATCH 0/6] pcie: fixes for pci branch Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 1/6] pcie: fix pcie_cap_slot_write_config() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 2/6] pcie/slot: fix hotplug_event_notify() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 3/6] pcie/slot: clean up of hotplug_event_notify() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 4/6] pcie/slot: factor out the logic to update hotplug event status Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 5/6] pcie/slot: fix save/load Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 6/6] msix: remove range checks Isaku Yamahata
2010-10-27 14:52   ` Michael S. Tsirkin [this message]
2010-10-27 16:40 ` [Qemu-devel] Re: [PATCH 0/6] pcie: fixes for pci branch Michael S. Tsirkin
2010-10-28  2:45   ` Isaku Yamahata

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=20101027145206.GA4074@redhat.com \
    --to=mst@redhat.com \
    --cc=etmartin@cisco.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skandasa@cisco.com \
    --cc=wexu2@cisco.com \
    --cc=yamahata@valinux.co.jp \
    /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).