public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: konrad@kernel.org, xen-devel@lists.xenproject.org,
	david.vrabel@citrix.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] xen-pciback: Document the various parameters and attributes in SysFS
Date: Mon, 14 Jul 2014 12:28:39 -0400	[thread overview]
Message-ID: <20140714162839.GA7609@laptop.dumpdata.com> (raw)
In-Reply-To: <53C04D27.3050807@oracle.com>

On Fri, Jul 11, 2014 at 04:46:31PM -0400, Boris Ostrovsky wrote:
> On 07/11/2014 04:08 PM, konrad@kernel.org wrote:
> >From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >
> >Which hadn't been done with the initial commit.
> >
> >Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >---
> >v2: Dropped the parameters and one that is unlikeable.
> >---
> >  Documentation/ABI/testing/sysfs-driver-pciback |   25 ++++++++++++++++++++++++
> >  1 files changed, 25 insertions(+), 0 deletions(-)
> >  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..e482240
> >--- /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@lists.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:
> >+                Device.Function-Register:Size:Mask (Domain is optional).
> >+                For example:
> >+                #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks
> >+                will allow the guest to read and write to the configuration
> >+                register 0x0E.
> >+
> >+What:           /sys/bus/pci/drivers/pciback/irq_handlers
> >+Date:           Oct 2011
> >+KernelVersion:  3.1
> >+Contact:        xen-devel@lists.xenproject.org
> >+Description:
> >+                A list of all of the PCI devices owned by Xen PCI back and
> >+                whether Xen PCI backend will acknowledge the interrupts received
> >+                and the amount of interrupts received. Xen PCI back acknowledges
> >+                said interrupts only when they are level, shared with another
> >+                guest, and enabled by the guest.
> 
> There are 4 fields per device. This description misses isr_on.

Grrr. I missed this in my repost. Will fix it to say on the last line:
'guest, whether it will acknowledge interrupts, and enabled by the guest'.

> 
> -boris
> 

  reply	other threads:[~2014-07-14 16:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 20:08 [PATCH v4] PCI back fixes for 3.17 konrad
2014-07-11 20:08 ` [PATCH v4 1/5] xen-pciback: Document the various parameters and attributes in SysFS konrad
2014-07-11 20:46   ` Boris Ostrovsky
2014-07-14 16:28     ` Konrad Rzeszutek Wilk [this message]
2014-07-11 20:08 ` [PATCH v4 2/5] xen/pciback: Don't deadlock when unbinding konrad
2014-07-11 20:48   ` Boris Ostrovsky
2014-07-11 21:02     ` Konrad Rzeszutek Wilk
2014-07-14 14:13       ` Konrad Rzeszutek Wilk
2014-07-14 14:30         ` Boris Ostrovsky
2014-07-14 15:42           ` Konrad Rzeszutek Wilk
2014-07-11 20:08 ` [PATCH v4 3/5] xen/pciback: Include the domain id if removing the device whilst still in use konrad
2014-07-11 20:08 ` [PATCH v4 4/5] xen/pciback: Print out the domain owning the device konrad
2014-07-11 20:08 ` [PATCH v4 5/5] xen/pciback: Remove tons of dereferences konrad
2014-07-11 20:54   ` Boris Ostrovsky
2014-07-14 16:37 ` [Xen-devel] [PATCH v4] PCI back fixes for 3.17 Sander Eikelenboom
2014-07-14 17:22   ` Konrad Rzeszutek Wilk
2014-07-14 17:29     ` Sander Eikelenboom
2014-07-14 17:37       ` Konrad Rzeszutek Wilk
2014-07-14 17:43         ` Sander Eikelenboom
2014-07-14 17:45           ` Konrad Rzeszutek Wilk
2014-07-14 18:24             ` Sander Eikelenboom
2014-07-14 18:45               ` Konrad Rzeszutek Wilk
2014-07-14 19:01                 ` Sander Eikelenboom
2014-07-14 19:50                   ` Sander Eikelenboom
2014-07-14 19:54                   ` Konrad Rzeszutek Wilk
2014-07-14 20:16                     ` Sander Eikelenboom
2014-07-14 20:18                       ` Konrad Rzeszutek Wilk
2014-07-14 20:21                         ` Sander Eikelenboom
2014-07-14 20:25                           ` Konrad Rzeszutek Wilk

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=20140714162839.GA7609@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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