On Tue, 2015-10-06 at 06:20 +0100, gre...@linuxfoundation.org wrote:
> On Tue, Oct 06, 2015 at 06:12:40AM +0100, gre...@linuxfoundation.org wrote:
> > On Mon, Oct 05, 2015 at 10:38:43AM -0700, Sudeep Dutt wrote:
> > > On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> > > > On Tue, 2015-0
On Tue, Oct 06, 2015 at 06:12:40AM +0100, gre...@linuxfoundation.org wrote:
> On Mon, Oct 05, 2015 at 10:38:43AM -0700, Sudeep Dutt wrote:
> > On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> > > On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> > > > From: Sudeep Dutt
> > > >
On Mon, Oct 05, 2015 at 10:38:43AM -0700, Sudeep Dutt wrote:
> On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> > On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> > > From: Sudeep Dutt
> > >
> > > iova is a library which can be built without IOMMU_SUPPORT
> > >
> > > Signed
On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> > From: Sudeep Dutt
> >
> > iova is a library which can be built without IOMMU_SUPPORT
> >
> > Signed-off-by: Sudeep Dutt
>
> The first three of these patches are in 4.3-rc4
Revert 'commit 353649e5da90 ("iommu: Allow iova to be used without
requiring IOMMU_SUPPORT"). This commit is made unnecessary by
'commit ac6d83ccd9c5 ("misc: mic: Fix SCIF build failure with
IOMMU_SUPPORT disabled") and will create a conflict upon merging
with 4.3-rc4. The correct long term solutio
Hi.
I think I rang the bell a bit early. The corruption is in grub legacy (I
assumed that would be in Linux too, but it wasn't). The on disk format
of ext4 apparently stores byte ordering somehow? I thought the on disk
format of ext4 was a specific endian (little). Since only that file is
unr
Never mind my ranting.
The problem was in the extent disk format of ext4. I had forgot that
ext4 uses extents for all new files by default. Old grub won't read extents.
Oh, well... nothing like wasting hard working peoples time with stupid
things. Anyway. SWIOTLB for 32-bit PAE should be a goo
Hi Mitch,
On Sat, Sep 26, 2015 at 01:12:05AM +0100, Mitchel Humpherys wrote:
> Currently we return IRQ_NONE from the context fault handler if the FSR
> doesn't actually have the fault bit set (some sort of miswired
> interrupt?) or if the client doesn't register an IOMMU fault handler.
> However,
On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> From: Sudeep Dutt
>
> iova is a library which can be built without IOMMU_SUPPORT
>
> Signed-off-by: Sudeep Dutt
The first three of these patches are in 4.3-rc4 already. Apologies for
the delay in pushing them out.
This one looks sane
On Mon, Oct 05, 2015 at 12:32:00PM +0200, Christoffer Dall wrote:
> [cc'ing Mark R. and Shannon for their input on FDT and ACPI].
>
> On Mon, Oct 05, 2015 at 11:07:35AM +0100, Peter Maydell wrote:
> > On 5 October 2015 at 10:37, Christoffer Dall
> > wrote:
> > > On Fri, Oct 02, 2015 at 11:53:07PM
[cc'ing Mark R. and Shannon for their input on FDT and ACPI].
On Mon, Oct 05, 2015 at 11:07:35AM +0100, Peter Maydell wrote:
> On 5 October 2015 at 10:37, Christoffer Dall
> wrote:
> > On Fri, Oct 02, 2015 at 11:53:07PM +0100, Peter Maydell wrote:
> >> * I don't really want to build in a lot of
On 5 October 2015 at 10:37, Christoffer Dall
wrote:
> On Fri, Oct 02, 2015 at 11:53:07PM +0100, Peter Maydell wrote:
>> * I don't really want to build in a lot of infrastructure into
>>QEMU to either build the DTC compiler into it or else introduce
>>a runtime dependency on the dtc binary
On Mon, Oct 5, 2015 at 11:53 AM, Christoffer Dall
wrote:
> [why are you top-posting?]
>
> On Mon, Oct 05, 2015 at 11:42:38AM +0200, Baptiste Reynal wrote:
>> In this patch series we want to wrap an already available kernel
>> interface to expose a device property to userspace,
>
> which 'already a
On Sat, Oct 03, 2015 at 02:00:19PM -0400, Konrad Rzeszutek Wilk wrote:
> Aye. I presume that you had done a small change already for this?
> Would you be willing to post it on lkml and CC me ?
Yes, I also think it is needed. SWIOTLB already correctly handles
buffers in HighMem, so enabling it for
[why are you top-posting?]
On Mon, Oct 05, 2015 at 11:42:38AM +0200, Baptiste Reynal wrote:
> In this patch series we want to wrap an already available kernel
> interface to expose a device property to userspace,
which 'already available kernel interface' is that exactly?
> in order to keep
> t
In this patch series we want to wrap an already available kernel
interface to expose a device property to userspace, in order to keep
the code lighter on the userspace. We need those properties in VFIO as
VFIO grants the possibility to develop userspace drivers.
The sysfs doesn't seems to be ready
On Fri, Oct 02, 2015 at 11:53:07PM +0100, Peter Maydell wrote:
> On 2 October 2015 at 21:28, Christoffer Dall
> wrote:
> > We discussed this for the purposes of ARM during SFO15 last week, and
> > basically arrived at the conclusion that the resonable thing to do is to
> > rely on sysfs device tre
17 matches
Mail list logo
