On 27.07.19 12:00, Marc-André Lureau wrote:
Hi
On Sat, Jul 27, 2019 at 10:16 AM Jan Kiszka wrote:
From: Jan Kiszka
I haven't been doing anything here for a long time, nor does my git repo
still play a role.
Signed-off-by: Jan Kiszka
too bad, we could still use some help ;)
thanks
If it's reproducible with real hardware, then it's definitely not a bug
of QEMU ==> Removing QEMU from this bug ticket.
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 11/8/2019 4:41 PM, Igor Mammedov wrote:
On Fri, 08 Nov 2019 09:05:52 +0100
Markus Armbruster wrote:
Tao Xu writes:
On 11/7/2019 9:31 PM, Eduardo Habkost wrote:
On Thu, Nov 07, 2019 at 02:24:52PM +0800, Tao Xu wrote:
On 11/7/2019 4:53 AM, Eduardo Habkost wrote:
On Mon, Oct 28, 2019 at
> My question would be "what is the actual problem you are trying to
> solve?".
One problem that needs to be solved is sharing buffers between
devices. With the out-of-tree Wayland device, to share virtio-gpu
buffers we've been using the virtio resource id. However, that
approach isn't
From: Dongjiu Geng
This patch implements APEI GHES Table generation via fw_cfg blobs. Now
it only supports ARMv8 SEA, a type of GHESv2 error source. Afterwards,
we can extend the supported types if needed. For the CPER section,
currently it is memory section because kernel mainly wants userspace
From: Dongjiu Geng
Add a SIGBUS signal handler. In this handler, it checks the SIGBUS type,
translates the host VA delivered by host to guest PA, then fills this PA
to guest APEI GHES memory, then notifies guest according to the SIGBUS
type.
When guest accesses the poisoned memory, it will
In the ARMv8 platform, the CPU error types are synchronous external abort(SEA)
and SError Interrupt (SEI). If exception happens in guest, sometimes it's better
for guest to perform the recovery, because host does not know the detailed
information of guest. For example, if an exception happens in a
From: Dongjiu Geng
kvm_hwpoison_page_add() and kvm_unpoison_all() will both be used by X86
and ARM platforms, so moving them into "accel/kvm/kvm-all.c" to avoid
duplicate code.
For architectures that don't use the poison-list functionality the
reset handler will harmlessly do nothing, so let's
From: Dongjiu Geng
Add APEI/GHES detailed design document
Signed-off-by: Dongjiu Geng
Signed-off-by: Xiang Zheng
Reviewed-by: Michael S. Tsirkin
---
docs/specs/acpi_hest_ghes.rst | 95 +++
docs/specs/index.rst | 1 +
2 files changed, 96
From: Dongjiu Geng
I and Xiang are willing to review the APEI-related patches and
volunteer as the reviewers for the APEI/GHES part.
Signed-off-by: Dongjiu Geng
Signed-off-by: Xiang Zheng
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
From: Dongjiu Geng
RAS Virtualization feature is not supported now, so add a RAS machine
option and disable it by default.
Signed-off-by: Dongjiu Geng
Signed-off-by: Xiang Zheng
---
hw/arm/virt.c | 23 +++
include/hw/arm/virt.h | 1 +
2 files changed, 24
On 2019/11/8 16:11, gengdongjiu wrote:
> On 2019/11/4 20:14, Xiang Zheng wrote:
>> From: Dongjiu Geng
>>
>> This patch implements APEI GHES Table generation via fw_cfg blobs. Now
>> it only supports ARMv8 SEA, a type of GHESv2 error source. Afterwards,
>> we can extend the supported types if
On 11/8/2019 9:44 PM, Igor Mammedov wrote:
On Thu, 7 Nov 2019 15:45:08 +0800
Tao Xu wrote:
From: Liu Jingqi
HMAT is defined in ACPI 6.3: 5.2.27 Heterogeneous Memory Attribute Table
(HMAT). The specification references below link:
On Sat, Nov 09, 2019 at 03:56:21PM +, Peter Maydell wrote:
> On Fri, 8 Nov 2019 at 19:48, Palmer Dabbelt wrote:
> >
> > This new helper function encodes the idiom used by the ARM virt board to
> > set a string array. I don't currently have a working ARM userspace, so I
> > haven't tested
>
On Fri, Nov 08, 2019 at 10:13:16AM -0800, Palmer Dabbelt wrote:
> On Fri, 08 Nov 2019 10:04:47 PST (-0800), Peter Maydell wrote:
> > On Fri, 8 Nov 2019 at 17:15, Alistair Francis wrote:
> > >
> > > On Fri, Nov 8, 2019 at 9:05 AM Palmer Dabbelt wrote:
> > > >
> > > > The test finisher implements
On Fri, Nov 08, 2019 at 06:04:47PM +, Peter Maydell wrote:
> On Fri, 8 Nov 2019 at 17:15, Alistair Francis wrote:
> >
> > On Fri, Nov 8, 2019 at 9:05 AM Palmer Dabbelt wrote:
> > >
> > > The test finisher implements the reset command, which means it's a
> > > "sifive,test1" device. This is
On Sat, Nov 09, 2019 at 03:59:24PM +, Peter Maydell wrote:
> On Fri, 8 Nov 2019 at 19:48, Palmer Dabbelt wrote:
> >
> > The device tree format allows for arrays of strings, which are encoded
> > with '\0's inside regular strings. These are ugly to represent in C, so
> > the helper function
On 10.11.2019 22:03, Denis Plotnikov wrote:
> This allows to change (replace) the file on a block device and is useful
> to workaround exclusive file access restrictions, e.g. to implement VM
> migration with a shared disk stored on some storage with the exclusive
> file opening model: a
Some device's property can be changed if the device has been already
realized. For example, it could be "drive" property of a scsi disk device.
So far, set_pointer could operate only on a relized device. The patch
extends its interface for operation on an unrealized device.
Signed-off-by: Denis
This allows to change (replace) the file on a block device and is useful
to workaround exclusive file access restrictions, e.g. to implement VM
migration with a shared disk stored on some storage with the exclusive
file opening model: a destination VM is started waiting for incomming
migration
This allows to replace the file on a block device and is useful
to workaround the cases (migration) when the VM image is placed on
some shared storage with exclusive file opening model but the image
should be open form more than one app.
The previous version of approaching the workaround was
On Sat, 9 Nov 2019 at 21:08, Aleksandar Markovic
wrote:
> Given modularity of RasPi, wouldn't it be nice for end users to be able to
> specify an RTC via command line?
The rtc option specifies properties of the backend of
an rtc device. It doesn't specify what the RTC device
exposed to the
22 matches
Mail list logo
