The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning, the runtime component of the firmware (RTAS) has
been implemented as a 2
I noticed https://wiki.qemu.org/Planning is outdated: 6.0 is listed
under Planning Pages, but at the top it says 5.0 is the release that's
currently in development.
--
Rebecca Cran
This new function to get the drm_format associated with a pixman
format will be useful while creating a dmabuf.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
include/ui/qemu-pixman.h | 1 +
ui/qemu-pixman.c | 35 ---
2 files changed
Add helper functions to create a dmabuf for a resource and mmap it.
To be able to create a dmabuf using the udmabuf driver, Qemu needs
to be lauched with the memfd memory backend like this:
qemu-system-x86_64 -m 8192m -object memory-backend-memfd,id=mem1,size=8192M
-machine memory-backend=mem1
Ba
Try to open the udmabuf dev node for the first time or return the
fd if the device was previously opened.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
include/ui/console.h | 3 +++
ui/meson.build | 1 +
ui/udmabuf.c | 40 +++
Store the meta-data associated with a FB in a new object
(struct virtio_gpu_framebuffer) and pass the object to set_scanout.
Also move code in set_scanout into a do_set_scanout function.
This will be helpful when adding set_scanout_blob API.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek K
Instead of passing the attach_backing object to extract nr_entries
and offset, explicitly pass these as arguments to this function.
This will be helpful when adding create_blob API.
Signed-off-by: Vivek Kasireddy
---
hw/display/virtio-gpu-3d.c | 3 ++-
hw/display/virtio-gpu.c| 22 ++
Enabling this feature would eliminate data copies from the resource
object in the Guest to the shadow resource in Qemu. This patch series
however adds support only for Blobs of type
VIRTIO_GPU_BLOB_MEM_GUEST with property VIRTIO_GPU_BLOB_FLAG_USE_SHAREABLE.
Most of the patches in this series are a
Add the property bit, configuration flag and other relevant
macros and definitions associated with this feature.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
hw/display/virtio-gpu-base.c | 3 +++
hw/display/virtio-gpu.c| 27 +++
include/
Move finding the resource and validating its backing storage into one
function.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
hw/display/virtio-gpu.c | 66 +
1 file changed, 47 insertions(+), 19 deletions(-)
diff --git a/hw/display/
This API allows Qemu to register the blob allocated by the Guest
as a new resource and map its backing storage.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
hw/display/trace-events | 1 +
hw/display/virtio-gpu-udmabuf.c | 9 +++-
hw/display/virtio-gpu.
These helpers can be useful for creating dmabuf objects from blobs
and submitting them to the UI.
Signed-off-by: Vivek Kasireddy
---
hw/display/virtio-gpu-udmabuf.c | 88 +
include/hw/virtio/virtio-gpu.h | 15 ++
2 files changed, 103 insertions(+)
diff --git
This API allows Qemu to set the blob allocated by the Guest as
the scanout buffer. If Opengl support is available, then the
scanout buffer would be submitted as a dmabuf to the UI; if not,
a pixman image is created from the scanout buffer and is
submitted to the UI via the display surface.
Based-o
If a blob is available for the cursor, copy the data from the blob.
Based-on-patch-by: Gerd Hoffmann
Signed-off-by: Vivek Kasireddy
---
hw/display/virtio-gpu.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gp
Patchew URL:
https://patchew.org/QEMU/20210331031001.1564125-1-vivek.kasire...@intel.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210331031001.1564125-1-vivek.kasire...@intel.com
Subject: [PATCH 00/11] Add sup
Thanks for looking into this patch,
David Gibson writes:
>> H_SCM_HEALTH specifications is already documented in linux kernel
>> documentation at
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/powerpc/papr_hcalls.rst
>
> Putting a reference to that in t
On Wed, 31 Mar 2021 11:09:06 +1100
David Gibson wrote:
> On Tue, Mar 30, 2021 at 08:01:13AM -0700, Richard Henderson wrote:
> > On 3/29/21 10:54 PM, David Gibson wrote:
> > >B) Just the hflags patches from my / Richard's tree
> > > https://gitlab.com/dgibson/qemu/-/pipelines/278497244
>
David Gibson writes:
> On Mon, Mar 29, 2021 at 03:32:37PM -0300, Daniel Henrique Barboza wrote:
...
>
>> We assign ibm,chip-id=0x0 to CPUs 0-3, but CPUs 2-3 are located in a
>> different NUMA node than 0-1. This would mean that the same socket
>> would belong to different NUMA nodes at the same ti
On 31/03/2021 04.53, Rebecca Cran wrote:
I noticed https://wiki.qemu.org/Planning is outdated: 6.0 is listed under
Planning Pages, but at the top it says 5.0 is the release that's currently
in development.
Thanks for the hint! I've simply removed that link now since we apparently
forgot to up
Hi Gerd,
Since the udmabuf and blob supports are on their way, can we reconsider the
display-drm ui support which was list in
https://git.kraxel.org/cgit/qemu/refs/heads as a branch before.
I did some rebasing work and can help to send them out for review if possible.
BR,
Tina
> -Original
On 30/03/2021 12.53, Paolo Bonzini wrote:
On 30/03/21 11:08, Thomas Huth wrote:
I've picked the Django Code of Conduct as a base, since it sounds rather
friendly and still welcoming to me, but I'm open for other suggestions, too
(but we should maybe pick one where the conflict resolution p
On Wed, Mar 31, 2021 at 06:04:27AM +0200, Greg Kurz wrote:
> On Wed, 31 Mar 2021 11:09:06 +1100
> David Gibson wrote:
>
> > On Tue, Mar 30, 2021 at 08:01:13AM -0700, Richard Henderson wrote:
> > > On 3/29/21 10:54 PM, David Gibson wrote:
> > > >B) Just the hflags patches from my / Richard's t
30.03.2021 19:39, Max Reitz wrote:
==
OK, I think now that you didn't mean qcow2_alloc_clusters(). So, we are saying about only
functions returning an offset to cluster with "guest data", not to any kind of
host cluster. Than what you propose looks like this to me:
- take my v5
- rename q
From: Alexey Kardashevskiy
There is no H_REGISTER_PROCESS_TABLE, it is H_REGISTER_PROC_TBL handler
for which is still called h_register_process_table() though.
Signed-off-by: Alexey Kardashevskiy
Message-Id: <20210225032335.64245-1-...@ozlabs.ru>
Reviewed-by: Daniel Henrique Barboza
Signed-off
From: Bin Meng
Per devicetree spec v0.3 [1] chapter 2.3.5:
The #address-cells and #size-cells properties are not inherited
from ancestors in the devicetree. They shall be explicitly defined.
If missing, a client program should assume a default value of 2
for #address-cells, and a value of 1 for
From: Greg Kurz
Each vCPU core exposes its timebase frequency in the DT. When running
under KVM, this means parsing /proc/cpuinfo in order to get the timebase
frequency of the host CPU.
The parsing appears to slow down the boot quite a bit with higher number
of cores:
# of cores seconds spe
From: Greg Kurz
spapr_memory_unplug() is the last step of the hot unplug sequence.
It is indirectly called by:
spapr_lmb_release()
hotplug_handler_unplug()
and spapr_lmb_release() already buys us that DIMM unplug state is
present : it gets restored with spapr_recover_pending_dimm_state()
if
The following changes since commit 6d40ce00c1166c317e298ad82ecf10e650c4f87d:
Update version for v6.0.0-rc1 release (2021-03-30 18:19:07 +0100)
are available in the Git repository at:
https://gitlab.com/dgibson/qemu.git tags/ppc-for-6.0-20210331
for you to fetch changes up to 611ac0a60fdcc74
On 3/30/21 10:47 PM, David Gibson wrote:
Richard - the remaining possible problem with the hflags stuff seems
to manifest with the assert failing in the last patch. However, I'm
guess that's just exposing some more subtle problem introduced by an
earlier patch. Any chance you could re-order the
From: Bin Meng
As the comment of tx_padding_and_crc() says: "Never add CRC in QEMU",
min_frame_len should excluce CRC, so it should be 60 instead of 64.
Signed-off-by: Bin Meng
Message-Id: <20210316081505.72898-1-bmeng...@gmail.com>
Signed-off-by: David Gibson
---
hw/net/fsl_etsec/rings.c | 2
The driver can query some bits in SMMUv3 IDR5 to learn which
translation granules are supported. Arm recommends that SMMUv3
implementations support at least 4K and 64K granules. But in
the vSMMUv3, there seems to be no reason not to support 16K
translation granule. In addition, if 16K is not suppor
Ah, perfect, I was missing dram_metadata.is_enabled.
And my userland unaligned test case demonstrates that
the second granule is tested, as reported.
** Changed in: qemu
Status: New => Confirmed
** Changed in: qemu
Status: Confirmed => In Progress
--
You received this bug notific
On 31/03/21 07:40, Thomas Huth wrote:
On 30/03/2021 12.53, Paolo Bonzini wrote:
On 30/03/21 11:08, Thomas Huth wrote:
I've picked the Django Code of Conduct as a base, since it sounds
rather
friendly and still welcoming to me, but I'm open for other
suggestions, too
(but we should maybe
201 - 233 of 233 matches
Mail list logo
