On 28/10/2021 07:50, Yong Wu wrote:
> We add the ostd setting for mt8195. It introduces a abort for the
> previous SoC which doesn't have ostd setting. This is the log:
>
> Unable to handle kernel NULL pointer dereference at virtual address
> 0080
> ...
> pc :
On Thu, Oct 28, 2021 at 02:07:46AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Tuesday, October 26, 2021 7:35 AM
> >
> > On Fri, Oct 22, 2021 at 03:08:06AM +, Tian, Kevin wrote:
> >
> > > > I have no idea what security model makes sense for wbinvd, that is the
> > > >
On Thu, Oct 28, 2021 at 04:39:40PM -0500, Rob Herring wrote:
> On Thu, 21 Oct 2021 01:17:00 +0200, David Heidelberg wrote:
> > Add missing compatible for the SDX55 SoC.
> >
> > Signed-off-by: David Heidelberg
> > ---
> > Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 1 +
> > 1 file
On Fri, Oct 29, 2021 at 11:15:31AM +1100, David Gibson wrote:
> > +Device must be bound to an iommufd before the attach operation can
> > +be conducted. The binding operation builds the connection between
> > +the devicefd (opened via device-passthrough framework) and IOMMUFD.
> >
Hi Jason,
> From: Jason Gunthorpe
> Sent: Monday, October 25, 2021 8:53 PM
>
> On Mon, Oct 25, 2021 at 06:28:09AM +, Liu, Yi L wrote:
> >thanks for the guiding. will also refer to your vfio_group_cdev series.
> >
> >Need to double confirm here. Not quite following on the kfree. Is
>
On Sun, Sep 19, 2021 at 02:38:48PM +0800, Liu Yi L wrote:
> Document the /dev/iommu framework for user.
>
> Open:
> Do we want to document /dev/iommu in Documentation/userspace-api/iommu.rst?
> Existing iommu.rst is for the vSVA interfaces, honestly, may need to rewrite
> this doc entirely.
>
>
