xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Subject: Re: [PATCH] serial: Skip over PCIe device which have no quirks (fix AMT regression).
Date: Wed, 5 Mar 2014 16:46:40 -0600	[thread overview]
Message-ID: <5317A950.7040103@amd.com> (raw)
In-Reply-To: <20140305210950.GB11758@phenom.dumpdata.com>

On 3/5/2014 3:09 PM, Konrad Rzeszutek Wilk wrote:
> See:
> 00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
>          Subsystem: Intel Corporation Device 2008
>          Flags: bus master, fast devsel, latency 0, IRQ 11
>          Memory at fb12a000 (64-bit, non-prefetchable) [size=16]
> 00:16.3 Serial controller: Intel Corporation Cougar Point KT Controller (rev 04) (prog-if 02 [16550])
>          Subsystem: Intel Corporation Device 2008
>          Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
>          I/O ports at f0e0 [size=8]
>          Memory at fb129000 (32-bit, non-prefetchable) [size=4K]
>
> pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
> pci 0000:00:16.3: [8086:1c3d] type 00 class 0x070002
>
> And Xen picks 00:16.0 as its console when using 'com1=115200,8n1,amt'.
>
> This patch fixes it and allows us to use AMT again by zeroing
> out io_base to zero. If the scan did not work, the io_base is
> set back to a default value.

If you provide 'amt' on command line => 'skip_amt' = 0
Then we'd just return -1 without setting io_base to 0x3f8 due to this 
condition-
if ( !skip_amt )
    return -1;

(or am I missing something?)

>
> diff --git a/xen/drivers/char/ns16550.c b/xen/drivers/char/ns16550.c
> index 487bf7d..9f87018 100644
> --- a/xen/drivers/char/ns16550.c
> +++ b/xen/drivers/char/ns16550.c
> @@ -829,6 +829,7 @@ pci_uart_config (struct ns16550 *uart, int skip_amt, int bar_idx)
>       unsigned int b, d, f, nextf, i;
>       u16 vendor, device;
>   
> +    uart->io_base = 0;

Why not set ns16550.io_base = 0; in arch/x86/setup.c ?
AFAICT, ns16550.c is the only one that uses ns16550_defaults structure, 
so it should be safe..


Thanks,
-Aravind.

  reply	other threads:[~2014-03-05 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 19:45 [PATCH] serial: Skip over PCIe device which have no quirks (fix AMT regression) Konrad Rzeszutek Wilk
2014-03-05 19:56 ` Konrad Rzeszutek Wilk
2014-03-05 21:09   ` Konrad Rzeszutek Wilk
2014-03-05 22:46     ` Aravind Gopalakrishnan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-06  0:43 Konrad Rzeszutek Wilk
2014-03-06 21:33 ` Aravind Gopalakrishnan

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=5317A950.7040103@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@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;
as well as URLs for NNTP newsgroup(s).