Displaying 5 results from an estimated 5 matches for "bios_linker_loader_alloc".
2016 Nov 16
2
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
Hi,
On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 15/11/2016 15:36, Namhyung Kim wrote:
>> Hi,
>>
>> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 15/11/2016 06:06, Michael S. Tsirkin wrote:
>>>> On Tue, Nov 15, 2016 at 01:50:21PM +0900, Namhyung Kim
2016 Nov 16
2
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
Hi,
On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 15/11/2016 15:36, Namhyung Kim wrote:
>> Hi,
>>
>> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 15/11/2016 06:06, Michael S. Tsirkin wrote:
>>>> On Tue, Nov 15, 2016 at 01:50:21PM +0900, Namhyung Kim
2016 Nov 16
0
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
...a real system and it reserves 8KB). The first eight
bytes are needed for the record identifier interface, because there's no such
thing as 64-bit I/O ports, and the rest can be used for the actual buffer.
QEMU already has an interface to allocate RAM and patch the address into an
ACPI table (bios_linker_loader_alloc). Because this interface is actually meant
to load data from QEMU into the firmware (using the "fw_cfg" interface), you
would have to add a dummy 8KB file to fw_cfg using fw_cfg_add_file (for
example "etc/erst-memory"), it can be just full of zeros.
QEMU supports two chipsets,...
2016 Nov 18
3
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
...interface, because there's no such
> thing as 64-bit I/O ports, and the rest can be used for the actual buffer.
Is there a limit on the size? It'd be great if it can use a few MB..
>
> QEMU already has an interface to allocate RAM and patch the address into an
> ACPI table (bios_linker_loader_alloc). Because this interface is actually meant
> to load data from QEMU into the firmware (using the "fw_cfg" interface), you
> would have to add a dummy 8KB file to fw_cfg using fw_cfg_add_file (for
> example "etc/erst-memory"), it can be just full of zeros.
>
> QE...
2016 Nov 18
3
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
...interface, because there's no such
> thing as 64-bit I/O ports, and the rest can be used for the actual buffer.
Is there a limit on the size? It'd be great if it can use a few MB..
>
> QEMU already has an interface to allocate RAM and patch the address into an
> ACPI table (bios_linker_loader_alloc). Because this interface is actually meant
> to load data from QEMU into the firmware (using the "fw_cfg" interface), you
> would have to add a dummy 8KB file to fw_cfg using fw_cfg_add_file (for
> example "etc/erst-memory"), it can be just full of zeros.
>
> QE...