All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
	<xen-devel@lists.xenproject.org>
Cc: <david.vrabel@citrix.com>
Subject: Re: [Xen-devel] [PATCH v3 2/3] xen/pciback: avoid multiple entries in slot list
Date: Fri, 23 Sep 2016 11:15:31 +0100	[thread overview]
Message-ID: <57E500C3.1000209@citrix.com> (raw)
In-Reply-To: <c7dc0293-79f7-9d49-b1f7-5d6335bd9a7e@oracle.com>

On 22/09/16 22:02, Boris Ostrovsky wrote:
> On 09/22/2016 04:45 AM, Juergen Gross wrote:
>> The Xen pciback driver has a list of all pci devices it is ready to
>> seize. There is no check whether a to be added entry already exists.
>> While this might be no problem in the common case it might confuse
>> those which consume the list via sysfs.
>>
>> Modify the handling of this list by not adding an entry which already
>> exists. As this will be needed later split out the list handling into
>> a separate function.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>>  drivers/xen/xen-pciback/pci_stub.c | 39 ++++++++++++++++++++++++++++++--------
>>  1 file changed, 31 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/xen/xen-pciback/pci_stub.c b/drivers/xen/xen-pciback/pci_stub.c
>> index 79a9e4d..0179333 100644
>> --- a/drivers/xen/xen-pciback/pci_stub.c
>> +++ b/drivers/xen/xen-pciback/pci_stub.c
>> @@ -478,6 +478,36 @@ static int __init pcistub_init_devices_late(void)
>>  	return 0;
>>  }
>>  
>> +static void pcistub_device_id_add_list(struct pcistub_device_id *new,
>> +				       int domain, int bus, unsigned int devfn)

I think this should allocate the new pcistub_device_id if needed.  You
can pass in GFP flags if needed.

Then it can return the newly allocated one, or the existing one.

static struct pcistub_device_id *pcistub_device_id_add_list(
    int domain, int bus, unsigned int devfn)

David

  parent reply	other threads:[~2016-09-23 10:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  8:45 [PATCH v3 0/3] xen/pciback: support driver_override Juergen Gross
2016-09-22  8:45 ` [PATCH v3 1/3] xen/pciback: simplify pcistub device handling Juergen Gross
2016-09-22  8:45 ` Juergen Gross
2016-09-22 20:57   ` Boris Ostrovsky
2016-09-22 20:57   ` Boris Ostrovsky
2016-09-22  8:45 ` [PATCH v3 2/3] xen/pciback: avoid multiple entries in slot list Juergen Gross
2016-09-22 21:02   ` Boris Ostrovsky
2016-09-23  4:02     ` Juergen Gross
2016-09-23  4:02     ` Juergen Gross
2016-09-23 10:15     ` David Vrabel [this message]
2016-09-28 17:22       ` [Xen-devel] " Juergen Gross
2016-09-28 17:22       ` Juergen Gross
2016-09-23 10:15     ` David Vrabel
2016-09-22 21:02   ` Boris Ostrovsky
2016-09-22  8:45 ` Juergen Gross
2016-09-22  8:45 ` [PATCH v3 3/3] xen/pciback: support driver_override Juergen Gross
2016-09-22  8:45 ` Juergen Gross
2016-09-22 21:10   ` Boris Ostrovsky
2016-09-23  4:06     ` Juergen Gross
2016-09-23  4:06     ` Juergen Gross
2016-09-22 21:10   ` Boris Ostrovsky
2016-09-30 14:47 ` [PATCH v3 0/3] " David Vrabel
2016-09-30 14:47 ` [Xen-devel] " David Vrabel

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=57E500C3.1000209@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --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 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.