From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] virtio: remove explicit pci ids from virtio_pci.c
Date: Mon, 21 Jan 2008 22:22:27 +1100 [thread overview]
Message-ID: <200801212222.28266.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4794620E.7010900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Monday 21 January 2008 20:12:46 Avi Kivity wrote:
> Anthony Liguori wrote:
> > Rusty Russell wrote:
> >> Qumranet let us use their PCI vendor ID, with device ids >= 0x1000.
> >> We can specify that we accept all of them in the device ID table, and
> >> then return -ENODEV in the probe routine.
> >
> > I thought the device id range was smaller. Avi?
>
> Yes, 0x1000-0x10ff IIRC.
>
> Also, if we break compatibility in the future, won't this claim devices
> we don't actually support?
Yep, I reduced it to 0x1000 - 0x103F for the moment. We can always expand
long before we get our 64th device type.
Cheers,
Rusty.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-21 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 0:30 [PATCH] virtio: remove explicit pci ids from virtio_pci.c Rusty Russell
[not found] ` <200801211130.51401.rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2008-01-21 4:34 ` Anthony Liguori
[not found] ` <479420D2.7050902-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-21 9:12 ` Avi Kivity
[not found] ` <4794620E.7010900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-21 11:22 ` Rusty Russell [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=200801212222.28266.rusty@rustcorp.com.au \
--to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox