All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Andreas Faerber <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 4/4] virtio-rng: hardware random number generator device
Date: Wed, 11 Jul 2012 12:32:50 +0300	[thread overview]
Message-ID: <4FFD4842.6010704@redhat.com> (raw)
In-Reply-To: <20120706120603.GA6446@amit.redhat.com>

On 07/06/2012 03:06 PM, Amit Shah wrote:
> On (Tue) 26 Jun 2012 [08:01:20], Anthony Liguori wrote:
>> >On 06/26/2012 05:48 AM, Amit Shah wrote:
>>> > >On (Mon) 25 Jun 2012 [17:59:28], Anthony Liguori wrote:
>>>> > >>On 06/25/2012 05:46 PM, Anthony Liguori wrote:
>>>>> > >>>From: Amit Shah<amit.shah@redhat.com>
>>> > >
>>>>> > >>>diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c
>>> > >
>>>>> > >>>+static void virtio_rng_class_init(ObjectClass *klass, void *data)
>>>>> > >>>+{
>>>>> > >>>+    DeviceClass *dc = DEVICE_CLASS(klass);
>>>>> > >>>+    PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
>>>>> > >>>+
>>>>> > >>>+    k->init = virtio_rng_init_pci;
>>>>> > >>>+    k->exit = virtio_rng_exit_pci;
>>>>> > >>>+    k->vendor_id = PCI_VENDOR_ID_REDHAT_QUMRANET;
>>>>> > >>>+    k->device_id = PCI_DEVICE_ID_VIRTIO_RNG;
>>>>> > >>>+    k->revision = VIRTIO_PCI_ABI_VERSION;
>>>>> > >>>+    k->class_id = PCI_CLASS_OTHERS;
>>>> > >>
>>>> > >>WHQL tends to get very particular about PCI classes.  Do we
>>>> > >>understand the implications of making this CLASS_OTHERS and WHQL?
>>> > >
>>> > >I've not asked around; will update with info when I get it.
>> >
>> >Thanks.
> ... and I heard back: PCI_CLASS_OTHERS is fine; no problem.
>

Unclassified device (PCI_CLASS_OTHERS) is the easiest way to pass M$ 
WHQL. It doesn't do any functional tests to the device itself, unlike 
NICs/StorPort devices. If M$ had a specific entropy device type it would 
be good to use it but I doubt such exist.

      reply	other threads:[~2012-07-11  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1340664362-25603-1-git-send-email-aliguori@us.ibm.com>
2012-07-01 22:06 ` [Qemu-devel] [RFC PATCH 0/4] virtio-rng and RngBackend infrastructure (v2) Paul Brook
2012-07-04 11:46   ` Amit Shah
     [not found] ` <1340664362-25603-5-git-send-email-aliguori@us.ibm.com>
     [not found]   ` <4FE8ED50.3090803@us.ibm.com>
     [not found]     ` <20120626104851.GF11372@amit.redhat.com>
     [not found]       ` <4FE9B2A0.2030002@us.ibm.com>
2012-07-06 12:06         ` [Qemu-devel] [PATCH 4/4] virtio-rng: hardware random number generator device Amit Shah
2012-07-11  9:32           ` Dor Laor [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=4FFD4842.6010704@redhat.com \
    --to=dlaor@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@linux.vnet.ibm.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 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.