From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] PCI: bus scan adjustments
Date: Tue, 11 Sep 2012 14:11:50 +0100 [thread overview]
Message-ID: <CC74F726.4B6F6%keir@xen.org> (raw)
In-Reply-To: <504F3CC7020000780009A8C7@nat28.tlf.novell.com>
On 11/09/2012 12:29, "Jan Beulich" <JBeulich@suse.com> wrote:
> As done elsewhere, the ns16550 code shouldn't look at non-zero
> functions of a device if that isn't multi-function.
>
> Also both there and in pass-through's _scan_pci_devices() skip looking
> at non-zero functions when the device at function zero doesn't exist.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> Note that to apply cleanly, this has to go on top of the serial console
> improvement series posted earlier.
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/drivers/char/ns16550.c
> +++ b/xen/drivers/char/ns16550.c
> @@ -470,21 +470,28 @@ static int
> pci_uart_config (struct ns16550 *uart, int skip_amt, int bar_idx)
> {
> uint32_t bar, len;
> - int b, d, f;
> + int b, d, f, nextf;
>
> /* NB. Start at bus 1 to avoid AMT: a plug-in card cannot be on bus 0. */
> for ( b = skip_amt ? 1 : 0; b < 0x100; b++ )
> {
> for ( d = 0; d < 0x20; d++ )
> {
> - for ( f = 0; f < 0x8; f++ )
> + for ( f = 0; f < 8; f = nextf )
> {
> + nextf = (f || (pci_conf_read16(0, b, d, f, PCI_HEADER_TYPE) &
> + 0x80)) ? f + 1 : 8;
> +
> switch ( pci_conf_read16(0, b, d, f, PCI_CLASS_DEVICE) )
> {
> case 0x0700: /* single port serial */
> case 0x0702: /* multi port serial */
> case 0x0780: /* other (e.g serial+parallel) */
> break;
> + case 0xffff:
> + if ( !f )
> + nextf = 8;
> + /* fall through */
> default:
> continue;
> }
> --- a/xen/drivers/passthrough/pci.c
> +++ b/xen/drivers/passthrough/pci.c
> @@ -665,7 +665,11 @@ static int __init _scan_pci_devices(stru
> for ( func = 0; func < 8; func++ )
> {
> if ( pci_device_detect(pseg->nr, bus, dev, func) == 0 )
> + {
> + if ( !func )
> + break;
> continue;
> + }
>
> pdev = alloc_pdev(pseg, bus, PCI_DEVFN(dev, func));
> if ( !pdev )
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-09-11 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 11:29 [PATCH] PCI: bus scan adjustments Jan Beulich
2012-09-11 13:11 ` Keir Fraser [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=CC74F726.4B6F6%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).