qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] mark nic as trusted


From: Gleb Natapov
Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted
Date: Wed, 7 Jan 2009 18:02:55 +0200

On Wed, Jan 07, 2009 at 03:41:32PM +0000, Mark McLoughlin wrote:
> On Wed, 2009-01-07 at 17:19 +0200, Gleb Natapov wrote:
> 
> > > > +    if (nd->secure_cookie[0])
> > > > +        pci_add_capability(&n->vdev.pci_dev, 0x0f, 0xf0, 
> > > > nd->secure_cookie, 14);
> > > 
> > > How was the Capability ID 0x0f chosen? It it unallocated by the PCI SIG
> > > allocated it or ...? I see it's not defined in the kernel sources:
> > > 
> > > #define  PCI_CAP_ID_AGP3        0x0E    /* AGP Target PCI-PCI bridge */
> > > #define  PCI_CAP_ID_EXP         0x10    /* PCI Express */
> > > 
> > It is "secure device capability", so I used it based on the name.
> 
> Ah, I see this in pciutils now:
> 
>   #define  PCI_CAP_ID_SECURE      0x0F    /* Secure device (?) */
> 
> Where is the capability format published? I can't seem to find any
> specification for it ...
> 
Me too. The only thing I found is that AMD barcelona chipset uses it.
Look at page 260 of this doc for details how:
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/31116_PUB_BKDG-3-18_11-13-08.pdf

I just hijacked the capability for our needs :)

--
                        Gleb.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]