On Tue May 14, 2024 at 12:23 PM UTC, Mickaël Salaün wrote:
> > Development happens
> > https://github.com/vianpl/{linux,qemu,kvm-unit-tests} and the vsm-next
> > branch, but I'd advice against looking into it until we add some order
> > to the rework. Regardless, feel free to get in touch.
>
> Than
On Tue May 7, 2024 at 4:16 PM UTC, Sean Christopherson wrote:
> > If yes, that would indeed require a *lot* of work for something we're not
> > sure will be accepted later on.
>
> Yes and no. The AWS folks are pursuing VSM support in KVM+QEMU, and SVSM
> support
> is trending toward the paired VM
Hi All,
On Tue, 2021-01-12 at 16:03 -0800, Florian Fainelli wrote:
> On 1/5/21 7:41 PM, Claire Chang wrote:
> > Add the initialization function to create restricted DMA pools from
> > matching reserved-memory nodes in the device tree.
> >
> > Signed-off-by: Claire Chang
> > ---
> > include/linu
On Mon, 2019-10-14 at 16:28 +0800, Shawn Guo wrote:
> On Tue, Sep 24, 2019 at 08:12:38PM +0200, Nicolas Saenz Julienne wrote:
> > qoriq-mc's dpmacs DMA configuration is inherited from their parent node,
> > which acts a bus in this regard. So far it maked all devices as
> &g
> > > > Robin, have you looked into supporting multiple dma-ranges? It's the
> > > > next thing
> > > > we need for BCM STB's PCIe. I'll have a go at it myself if nothing is in
> > > > the
> > > > works already.
> > >
> > > Multiple dma-ranges as far as configuring inbound windows should work
> >
Cc: Robin Murphy
> Cc: Julien Grall
> Cc: Nicolas Saenz Julienne
> Cc: Oleksandr Andrushchenko
> Cc: Boris Ostrovsky
> Cc: Juergen Gross
> Cc: Stefano Stabellini
> Cc: xen-devel@lists.xenproject.org
> Signed-off-by: Rob Herring
Just so it isn't forgotten, the
On Wed, 2019-09-25 at 16:09 +0100, Robin Murphy wrote:
> On 25/09/2019 15:52, Nicolas Saenz Julienne wrote:
> > On Tue, 2019-09-24 at 16:59 -0500, Rob Herring wrote:
> > > On Tue, Sep 24, 2019 at 1:12 PM Nicolas Saenz Julienne
> > > wrote:
> > > > Hi All,
&
On Tue, 2019-09-24 at 16:59 -0500, Rob Herring wrote:
> On Tue, Sep 24, 2019 at 1:12 PM Nicolas Saenz Julienne
> wrote:
> > Hi All,
> > this series tries to address one of the issues blocking us from
> > upstreaming Broadcom's STB PCIe controller[1]. Namely,
'len' in of_dma_get_range() is used to check the 'dma-ranges' property
length. After the fact, some calculations are run on the variable to be
then left unused.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/address.c | 5 ++---
1 file changed, 2 insertions(+), 3 dele
which takes the given DT node as the
device's underlying bus and parses it accordingly.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/bus/fsl-mc/fsl-mc-bus.c | 2 +-
drivers/gpu/host1x/bus.c| 2 +-
drivers/of/device.c | 30 --
driver
Some devices don't have their own OF node, and are stuck passing their
bus node. Adapt the function for this use case.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/address.c | 33 +++--
drivers/of/device.c| 3 ++-
include/linux/of_addr
The bus behind the board's PCIe core has DMA addressing limitations. Add
an empty 'dma-ranges' property on all PCIe bus descriptions to inform
the OF core that a translation is due further down the line.
Signed-off-by: Nicolas Saenz Julienne
---
arch/arm64/boot/dts/freescale/f
case, and make code a little more
explicit, create of_dma_config_copy() which will take another device's
DT node as an argument and simplify of_dma_config() by removing one of
it's redundant arguments.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/base/platform.c
The function provides the cell sizes for a specific bus type. Instead of
passing it the device DT node sitting on top of that bus we directly
pass its parent which is the actual node the function will start looking
from.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/address.c | 18
It's not longer advised to use notifiers in order to setup custom DMA
ops.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/device.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/of/device.c b/drivers/of/device.c
index 267b509df517..018c52688546 100644
--- a/drive
around the new function.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/address.c | 60 ++--
1 file changed, 36 insertions(+), 24 deletions(-)
diff --git a/drivers/of/address.c b/drivers/of/address.c
index 9c1e638fa8ea..c9eb4ebcc2e9 100644
--- a
qoriq-mc's node in order for DT's DMA
configuration code to get the DMA constraints from it.
Signed-off-by: Nicolas Saenz Julienne
---
arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 1 +
arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi | 1 +
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
The function was only available locally to of/address.c, make it
available to the OF subsystem.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/address.c| 18 --
drivers/of/base.c | 25 +
drivers/of/of_private.h | 2 ++
3 files changed
hacky usages that can be properly fixed as I show with the
DT fixes on the Layerscape platform.
This was also tested on a Raspberry Pi 4 with a custom PCIe driver and
on a Seattle AMD board.
Regards,
Nicolas
[1] https://patchwork.kernel.org/patch/9650345/#20294961
[2] https://patchwork.kernel.or
lls_parent() in order to deal with this limitation.
For now, it'll only be available privately to OF code.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/base.c | 44 +
drivers/of/of_private.h | 3 +++
2 files changed, 34 insertions(+
20 matches
Mail list logo
