lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 1 Aug 2014 15:59:42 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Greg KH <gregkh@...uxfoundation.org>,
	David Vrabel <david.vrabel@...rix.com>
CC:	<xen-devel@...ts.xenproject.org>, <boris.ostrovsky@...cle.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH v5 1/6] xen-pciback: Document the various
 parameters and attributes in SysFS

On 28/07/14 15:56, Greg KH wrote:
> On Mon, Jul 28, 2014 at 02:04:18PM +0100, David Vrabel wrote:
>> On 14/07/14 17:18, Konrad Rzeszutek Wilk wrote:
>>> Which hadn't been done with the initial commit.
>>>
>>> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
>>> ---
>>> v2: Dropped the parameters and one that is unlikeable.
>>> ---
>>>  Documentation/ABI/testing/sysfs-driver-pciback | 25 +++++++++++++++++++++++++
>>>  1 file changed, 25 insertions(+)
>>>  create mode 100644 Documentation/ABI/testing/sysfs-driver-pciback
>>>
>>> diff --git a/Documentation/ABI/testing/sysfs-driver-pciback b/Documentation/ABI/testing/sysfs-driver-pciback
>>> new file mode 100644
>>> index 0000000..cdc8340
>>> --- /dev/null
>>> +++ b/Documentation/ABI/testing/sysfs-driver-pciback
>>> @@ -0,0 +1,25 @@
>>> +What:           /sys/bus/pci/drivers/pciback/quirks
>>> +Date:           Oct 2011
>>> +KernelVersion:  3.1
>>> +Contact:        xen-devel@...ts.xenproject.org
>>> +Description:
>>> +                If the permissive attribute is set, then writing a string in
>>> +                the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
>>> +                to write and read from the PCI device. That is Domain:Bus:
>>
>> "...write and read the PCI device's configuration space."
> 
> How is this different from the normal pci device config file?

This is setting the permissions for a guest to access the real hardware
PCI config space (instead of the virtualized config space which the
guest has access to by default).

The guest access the config space using the normal methods (the file or
the kernel functions).

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ