From: Jan Beulich <jbeulich@suse.com>
To: Rahul Singh <Rahul.Singh@arm.com>
Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 1/3] xen/ns16550: Make ns16550 driver usable on ARM with HAS_PCI enabled.
Date: Wed, 18 Nov 2020 16:16:47 +0100 [thread overview]
Message-ID: <1530c2fb-8def-37eb-8a22-d7f9fc4e38b4@suse.com> (raw)
In-Reply-To: <CBBE4253-F244-418D-9EA6-BC39D1BC8DF8@arm.com>
On 18.11.2020 16:02, Rahul Singh wrote:
> Hello Jan,
>
>> On 17 Nov 2020, at 10:55 am, Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 16.11.2020 13:25, Rahul Singh wrote:
>>> NS16550 driver has PCI support that is under HAS_PCI flag. When HAS_PCI
>>> is enabled for ARM, compilation error is observed for ARM architecture
>>> because ARM platforms do not have full PCI support available.
>>
>> While you've extended the sentence, it remains unclear to me what
>> compilation error it is that results here. I've requested such
>> clarification for v2 already.
>
> Compilation error is related to the code that refer to x86 functions (create_irq()..) and MSI implementation related error.
> For more details please find the attached file for compilation error.
The use of mmio_ro_ranges is almost quite possibly going to remain
x86-specific, but then I guess this wants abstracting in a suitable
way.
The remaining look to all be MSI-related, so perhaps what you want
to avoid is just that part rather than everything PCI-ish?
>>> --- a/xen/drivers/char/ns16550.c
>>> +++ b/xen/drivers/char/ns16550.c
>>> @@ -16,7 +16,7 @@
>>> #include <xen/timer.h>
>>> #include <xen/serial.h>
>>> #include <xen/iocap.h>
>>> -#ifdef CONFIG_HAS_PCI
>>> +#ifdef CONFIG_HAS_NS16550_PCI
>>> #include <xen/pci.h>
>>> #include <xen/pci_regs.h>
>>> #include <xen/pci_ids.h>
>>
>> ... #undef-ining CONFIG_HAS_PCI at a suitable position in this
>> file (e.g. after all #include-s, to make sure all structure
>> layouts remain correct)? This would then be far easier to revert
>> down the road, and would confine the oddity to a single file
>> (and there a single place) in the code base.
>>
>
> As for ARM platforms, PCI implementation is in the development process and I am not sure if after completion of PCI work, ns16500 PCI part of code will work out of the box. I think there is some effort required to test the ns16550 PCI part of the code on ARM.
> As this code is tested on X86 only so I make the options depends on X86 and enable it by default for x86.
>
> I feel that adding a new Kconfig options is ok to enable/disable the PCI NS16550 support as compared to #undef CONFIG_HAS_PCI in the particular file. If in future other architecture wants to implement the PCI they will face the similar compilation error issues.
>
> Please suggest how we can proceed on this.
Introduce CONFIG_HAS_PCI_MSI (selected only by x86), if there's no
immediate plan to support it on Arm together with the rest of PCI?
Jan
next prev parent reply other threads:[~2020-11-18 15:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 12:25 [PATCH v3 0/3] xen/arm: Make PCI passthrough code non-x86 specific Rahul Singh
2020-11-16 12:25 ` [PATCH v3 1/3] xen/ns16550: Make ns16550 driver usable on ARM with HAS_PCI enabled Rahul Singh
2020-11-17 1:11 ` Stefano Stabellini
2020-11-17 10:55 ` Jan Beulich
2020-11-18 15:02 ` Rahul Singh
2020-11-18 15:16 ` Jan Beulich [this message]
2020-11-18 15:35 ` Julien Grall
2020-11-19 8:56 ` Jan Beulich
2020-11-19 9:00 ` Jan Beulich
2020-11-19 9:45 ` Julien Grall
2020-11-18 15:50 ` Julien Grall
2020-11-19 9:05 ` Jan Beulich
2020-11-19 9:21 ` Julien Grall
2020-11-19 9:53 ` Jan Beulich
2020-11-19 10:16 ` Julien Grall
2020-11-19 15:54 ` Rahul Singh
2020-11-19 16:22 ` Jan Beulich
2020-11-19 23:37 ` Stefano Stabellini
2020-11-19 23:50 ` Julien Grall
2020-11-20 0:14 ` Stefano Stabellini
2020-11-23 11:54 ` Rahul Singh
2020-11-23 13:19 ` Jan Beulich
2020-11-23 22:38 ` Stefano Stabellini
2020-11-23 17:13 ` Julien Grall
2020-11-24 9:47 ` Jan Beulich
2020-11-24 10:22 ` Julien Grall
2020-11-24 10:49 ` Jan Beulich
2020-11-16 12:25 ` [PATCH v3 2/3] xen/pci: Move x86 specific code to x86 directory Rahul Singh
2020-11-17 1:20 ` Stefano Stabellini
2020-11-17 9:49 ` Rahul Singh
2020-11-17 11:03 ` Jan Beulich
2020-11-17 16:52 ` Rahul Singh
2020-11-16 12:25 ` [PATCH v3 3/3] xen/pci: solve compilation error on ARM with HAS_PCI enabled Rahul Singh
2020-11-17 11:12 ` Jan Beulich
2020-11-17 16:15 ` Rahul Singh
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=1530c2fb-8def-37eb-8a22-d7f9fc4e38b4@suse.com \
--to=jbeulich@suse.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Rahul.Singh@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.