From: Sasha Levin <levinsasha928@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] virtio-net: Read MAC only after initializing MSI-X
Date: Tue, 16 Aug 2011 01:17:07 +0300 [thread overview]
Message-ID: <1313446627.3004.2.camel@sasha> (raw)
In-Reply-To: <87vctz7c7d.fsf@rustcorp.com.au>
On Mon, 2011-08-15 at 09:55 +0930, Rusty Russell wrote:
> On Sun, 14 Aug 2011 16:57:32 +0300, Sasha Levin <levinsasha928@gmail.com> wrote:
> > On Sun, 2011-08-14 at 12:23 +0930, Rusty Russell wrote:
> > > On Sat, 13 Aug 2011 11:51:01 +0300, Sasha Levin <levinsasha928@gmail.com> wrote:
> > > > The MAC of a virtio-net device is located at the first field of the device
> > > > specific header. This header is located at offset 20 if the device doesn't
> > > > support MSI-X or offset 24 if it does.
> > >
> > > Erk. This means, in general, we have to do virtio_find_single_vq or
> > > config->find_vqs before we examine any config options.
> > >
> > > Look at virtio_blk, which has the same error.
> > >
> > > Solutions in order of best to worst:
> > > (1) Enable MSI-X before calling device probe. This means reserving two
> > > vectors in virtio_pci_probe to ensure we *can* do this, I think. Michael?
> >
> > Do you mean reserving the vectors even before we probed the device for
> > MSI-X support? Wouldn't we need 3 vectors then? (config, input, output).
>
> We want three, but *need* two: see vp_find_vqs(). Also, the generic
> code doesn't know how many virtqueues we have on the device.
We can just pci_enable_msix() and see if we can get 2 vectors, if we can
- we assume the device has msix on, right?
--
Sasha.
next prev parent reply other threads:[~2011-08-15 22:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 8:51 [PATCH] virtio-net: Read MAC only after initializing MSI-X Sasha Levin
2011-08-14 2:53 ` Rusty Russell
2011-08-14 2:53 ` Rusty Russell
2011-08-14 13:57 ` Sasha Levin
2011-08-14 13:57 ` Sasha Levin
2011-08-15 0:25 ` Rusty Russell
2011-08-15 0:25 ` Rusty Russell
2011-08-15 22:17 ` Sasha Levin [this message]
2011-08-15 22:17 ` Sasha Levin
2011-08-19 15:23 ` Michael S. Tsirkin
2011-08-19 16:33 ` Sasha Levin
2011-08-20 20:00 ` Michael S. Tsirkin
2011-08-20 20:00 ` Michael S. Tsirkin
2011-09-19 3:35 ` Rusty Russell
2011-09-19 6:01 ` Michael S. Tsirkin
2011-09-19 7:49 ` Rusty Russell
2011-09-28 18:30 ` Sasha Levin
2011-10-02 9:11 ` Michael S. Tsirkin
2011-10-02 9:09 ` Michael S. Tsirkin
2011-10-03 23:51 ` Rusty Russell
2011-08-19 16:33 ` Sasha Levin
2011-08-22 0:24 ` Rusty Russell
2011-08-22 0:24 ` Rusty Russell
2011-08-22 8:36 ` Michael S. Tsirkin
2011-08-22 8:36 ` Michael S. Tsirkin
2011-08-23 3:49 ` Rusty Russell
2011-08-23 3:49 ` Rusty Russell
2011-08-31 16:24 ` Sasha Levin
2011-08-31 16:24 ` Sasha Levin
2011-08-19 15:23 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2011-08-13 8:51 Sasha Levin
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=1313446627.3004.2.camel@sasha \
--to=levinsasha928@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.