On Tue, 28 Jul 2020, Roger Pau Monné wrote:
> On Mon, Jul 27, 2020 at 05:06:25PM -0700, Stefano Stabellini wrote:
> > On Mon, 27 Jul 2020, Roger Pau Monné wrote:
> > > On Sat, Jul 25, 2020 at 10:59:50AM +0100, Julien Grall wrote:
> > > > On Sat, 25 Jul 2020 at 00:46, Stefano Stabellini
> > > >
On Mon, Jul 27, 2020 at 05:06:25PM -0700, Stefano Stabellini wrote:
> On Mon, 27 Jul 2020, Roger Pau Monné wrote:
> > On Sat, Jul 25, 2020 at 10:59:50AM +0100, Julien Grall wrote:
> > > On Sat, 25 Jul 2020 at 00:46, Stefano Stabellini
> > > wrote:
> > > >
> > > > On Fri, 24 Jul 2020, Julien
On Tue, Jul 28, 2020 at 08:06:17AM +, Rahul Singh wrote:
>
>
> > On 24 Jul 2020, at 3:44 pm, Roger Pau Monné wrote:
> >
> > On Thu, Jul 23, 2020 at 04:40:21PM +0100, Rahul Singh wrote:
> >> +
> >> +struct pci_host_bridge *bridge = pci_find_host_bridge(sbdf.seg,
> >> sbdf.bus);
> >> +
> On 24 Jul 2020, at 3:44 pm, Roger Pau Monné wrote:
>
> On Thu, Jul 23, 2020 at 04:40:21PM +0100, Rahul Singh wrote:
>> XEN during boot will read the PCI device tree node “reg” property
>> and will map the PCI config space to the XEN memory.
>>
>> XEN will read the “linux, pci-domain”
On Mon, 27 Jul 2020, Roger Pau Monné wrote:
> On Sat, Jul 25, 2020 at 10:59:50AM +0100, Julien Grall wrote:
> > On Sat, 25 Jul 2020 at 00:46, Stefano Stabellini
> > wrote:
> > >
> > > On Fri, 24 Jul 2020, Julien Grall wrote:
> > > > On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini
> > > >
> On 24 Jul 2020, at 9:23 am, Julien Grall wrote:
>
> Hi Rahul,
>
> On 23/07/2020 16:40, Rahul Singh wrote:
>> XEN during boot will read the PCI device tree node “reg” property
>> and will map the PCI config space to the XEN memory.
>> XEN will read the “linux, pci-domain” property from the
> On 24 Jul 2020, at 9:05 am, Julien Grall wrote:
>
> Hi,
>
> On 24/07/2020 08:03, Oleksandr Andrushchenko wrote:
diff --git a/xen/arch/arm/pci/pci-access.c b/xen/arch/arm/pci/pci-access.c
new file mode 100644
index 00..c53ef58336
--- /dev/null
+++
> On 24 Jul 2020, at 8:03 am, Oleksandr Andrushchenko
> wrote:
>
>
> On 7/24/20 2:38 AM, Stefano Stabellini wrote:
>> + Jan, Andrew, Roger
>>
>> Please have a look at my comment on whether we should share the MMCFG
>> code below, feel free to ignore the rest :-)
>>
>>
>> On Thu, 23 Jul
> On 24 Jul 2020, at 12:38 am, Stefano Stabellini
> wrote:
>
> + Jan, Andrew, Roger
>
> Please have a look at my comment on whether we should share the MMCFG
> code below, feel free to ignore the rest :-)
>
>
> On Thu, 23 Jul 2020, Rahul Singh wrote:
>> XEN during boot will read the PCI
On Sat, Jul 25, 2020 at 10:59:50AM +0100, Julien Grall wrote:
> On Sat, 25 Jul 2020 at 00:46, Stefano Stabellini
> wrote:
> >
> > On Fri, 24 Jul 2020, Julien Grall wrote:
> > > On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini
> > > wrote:
> > > > > If they are not equal, then I fail to see why
On Fri, Jul 24, 2020 at 05:54:20PM +0100, Julien Grall wrote:
> Hi Jan,
>
> On 24/07/2020 17:01, Jan Beulich wrote:
> > On 24.07.2020 17:15, Julien Grall wrote:
> > > On 24/07/2020 15:44, Roger Pau Monné wrote:
> > > > > +
> > > > > +struct pci_host_bridge *bridge =
On 25.07.2020 01:46, Stefano Stabellini wrote:
> On Fri, 24 Jul 2020, Julien Grall wrote:
>> On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini
>> wrote:
If they are not equal, then I fail to see why it would be useful to have
this
value in Xen.
>>>
>>> I think that's because the
On Sat, 25 Jul 2020 at 00:46, Stefano Stabellini wrote:
>
> On Fri, 24 Jul 2020, Julien Grall wrote:
> > On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini
> > wrote:
> > > > If they are not equal, then I fail to see why it would be useful to
> > > > have this
> > > > value in Xen.
> > >
> > > I
On Fri, 24 Jul 2020, Julien Grall wrote:
> On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini
> wrote:
> > > If they are not equal, then I fail to see why it would be useful to have
> > > this
> > > value in Xen.
> >
> > I think that's because the domain is actually more convenient to use
> >
On Fri, 24 Jul 2020 at 19:32, Stefano Stabellini wrote:
> > If they are not equal, then I fail to see why it would be useful to have
> > this
> > value in Xen.
>
> I think that's because the domain is actually more convenient to use
> because a segment can span multiple PCI host bridges. So my
>
On Fri, 24 Jul 2020, Julien Grall wrote:
> On 24/07/2020 18:41, Stefano Stabellini wrote:
> > On Fri, 24 Jul 2020, Julien Grall wrote:
> > > On 24/07/2020 00:38, Stefano Stabellini wrote:
> > > The segment number is just a value defined by the software. So as long as
> > > Linux and Xen agrees
On 24/07/2020 18:41, Stefano Stabellini wrote:
On Fri, 24 Jul 2020, Julien Grall wrote:
On 24/07/2020 00:38, Stefano Stabellini wrote:
The segment number is just a value defined by the software. So as long as
Linux and Xen agrees with the number, then we should be ok.
As far as I
On Fri, 24 Jul 2020, Julien Grall wrote:
> > > > +list_add_tail(>node, _host_bridges);
> > > It looks like _host_bridges should be an ordered list, ordered by
> > > segment number?
> >
> > Why? Do you expect bridge access in some specific order so ordered
> >
> > list will make it faster?
>
On Fri, 24 Jul 2020, Julien Grall wrote:
> On 24/07/2020 00:38, Stefano Stabellini wrote:
> > > +bridge->dt_node = dev;
> > > +bridge->sysdata = cfg;
> > > +bridge->ops = >pci_ops;
> > > +
> > > +if( !dt_property_read_u32(dev, "linux,pci-domain", ) )
> > > +{
> > > +
Hi Jan,
On 24/07/2020 17:01, Jan Beulich wrote:
On 24.07.2020 17:15, Julien Grall wrote:
On 24/07/2020 15:44, Roger Pau Monné wrote:
+
+struct pci_host_bridge *bridge = pci_find_host_bridge(sbdf.seg, sbdf.bus);
+
+if ( unlikely(!bridge) )
+{
+printk(XENLOG_ERR "Unable to
On 24.07.2020 17:15, Julien Grall wrote:
> On 24/07/2020 15:44, Roger Pau Monné wrote:
>>> +
>>> +struct pci_host_bridge *bridge = pci_find_host_bridge(sbdf.seg,
>>> sbdf.bus);
>>> +
>>> +if ( unlikely(!bridge) )
>>> +{
>>> +printk(XENLOG_ERR "Unable to find bridge for
On 24/07/2020 16:29, Roger Pau Monné wrote:
On Fri, Jul 24, 2020 at 04:15:47PM +0100, Julien Grall wrote:
On 24/07/2020 15:44, Roger Pau Monné wrote:
diff --git a/xen/arch/arm/pci/Makefile b/xen/arch/arm/pci/Makefile
new file mode 100644
index 00..358508b787
--- /dev/null
+++
On Fri, Jul 24, 2020 at 05:29:05PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 24, 2020 at 04:15:47PM +0100, Julien Grall wrote:
> >
> >
> > On 24/07/2020 15:44, Roger Pau Monné wrote:
> > > > +
> > > > +if ( acpi_disabled )
> > > > +dt_pci_init();
> > > > +else
> > > > +
On Fri, Jul 24, 2020 at 04:15:47PM +0100, Julien Grall wrote:
>
>
> On 24/07/2020 15:44, Roger Pau Monné wrote:
> > > diff --git a/xen/arch/arm/pci/Makefile b/xen/arch/arm/pci/Makefile
> > > new file mode 100644
> > > index 00..358508b787
> > > --- /dev/null
> > > +++
On 24/07/2020 15:44, Roger Pau Monné wrote:
diff --git a/xen/arch/arm/pci/Makefile b/xen/arch/arm/pci/Makefile
new file mode 100644
index 00..358508b787
--- /dev/null
+++ b/xen/arch/arm/pci/Makefile
@@ -0,0 +1,4 @@
+obj-y += pci.o
+obj-y += pci-host-generic.o
+obj-y +=
On Thu, Jul 23, 2020 at 04:40:21PM +0100, Rahul Singh wrote:
> XEN during boot will read the PCI device tree node “reg” property
> and will map the PCI config space to the XEN memory.
>
> XEN will read the “linux, pci-domain” property from the device tree
> node and configure the host bridge
Hi,
On 24/07/2020 00:38, Stefano Stabellini wrote:
+bridge->dt_node = dev;
+bridge->sysdata = cfg;
+bridge->ops = >pci_ops;
+
+if( !dt_property_read_u32(dev, "linux,pci-domain", ) )
+{
+printk(XENLOG_ERR "\"linux,pci-domain\" property in not available in
DT\n");
+
Hi Rahul,
On 23/07/2020 16:40, Rahul Singh wrote:
XEN during boot will read the PCI device tree node “reg” property
and will map the PCI config space to the XEN memory.
XEN will read the “linux, pci-domain” property from the device tree
node and configure the host bridge segment number
Hi,
On 24/07/2020 08:03, Oleksandr Andrushchenko wrote:
diff --git a/xen/arch/arm/pci/pci-access.c b/xen/arch/arm/pci/pci-access.c
new file mode 100644
index 00..c53ef58336
--- /dev/null
+++ b/xen/arch/arm/pci/pci-access.c
@@ -0,0 +1,101 @@
+/*
+ * Copyright (C) 2020 Arm Ltd.
I think
On 7/24/20 2:38 AM, Stefano Stabellini wrote:
> + Jan, Andrew, Roger
>
> Please have a look at my comment on whether we should share the MMCFG
> code below, feel free to ignore the rest :-)
>
>
> On Thu, 23 Jul 2020, Rahul Singh wrote:
>> XEN during boot will read the PCI device tree node “reg”
+ Jan, Andrew, Roger
Please have a look at my comment on whether we should share the MMCFG
code below, feel free to ignore the rest :-)
On Thu, 23 Jul 2020, Rahul Singh wrote:
> XEN during boot will read the PCI device tree node “reg” property
> and will map the PCI config space to the XEN
XEN during boot will read the PCI device tree node “reg” property
and will map the PCI config space to the XEN memory.
XEN will read the “linux, pci-domain” property from the device tree
node and configure the host bridge segment number accordingly.
As of now "pci-host-ecam-generic" compatible
32 matches
Mail list logo
