Albert Esteve writes:
> Add GET_SHMEM_CONFIG vhost-user frontend
> message to the spec documentation.
>
> Signed-off-by: Albert Esteve
> ---
> docs/interop/vhost-user.rst | 39 +
> 1 file changed, 39 insertions(+)
Reviewed-by: Alyssa
This happens because --static sets the prefer_static Meson option, but
my build machine doesn't have a static libpcre2. I don't think it
makes sense to insist that native dependencies are static, just
because I want the non-native QEMU binaries to be static.
Signed-off-by: Alyssa Ross
---
ta
Adding David Stevens, who implemented SHMEM_MAP and SHMEM_UNMAP in
crosvm a couple of years ago.
David, I'd be particularly interested for your thoughts on the MEM_READ
and MEM_WRITE commands, since as far as I know crosvm doesn't implement
anything like that. The discussion leading to those bein
On Mon, Mar 04, 2024 at 04:23:20PM -0800, Gurchetan Singh wrote:
> On Sat, Mar 2, 2024 at 6:38 AM Alyssa Ross wrote:
>
> > Hi Gurchetan,
> >
> > > >> > Would this be a suitable commit for the 0.1.3 release of rutabaga?
> > > >> >
>
Hi Gurchetan,
> >> > Would this be a suitable commit for the 0.1.3 release of rutabaga?
> >> >
> >> > https://chromium.googlesource.com/crosvm/crosvm/+/5dfd74a0680d317c6edf44138def886f47cb1c7c
> >> >
> >> > The gfxstream/AEMU commits would remain unchanged.
> >>
> >> That combination works for me.
Gurchetan Singh writes:
> On Sat, Jan 20, 2024 at 4:19 AM Alyssa Ross wrote:
>
>> Gurchetan Singh writes:
>>
>> > On Fri, Jan 19, 2024 at 1:13 PM Alyssa Ross wrote:
>> >>
>> >> Hi Gurchetan,
>> >>
>> >> > Thanks f
Gurchetan Singh writes:
> On Fri, Jan 19, 2024 at 1:13 PM Alyssa Ross wrote:
>>
>> Hi Gurchetan,
>>
>> > Thanks for the reminder. I did make a request to create the release
>> > tags, but changes were requested by Fedora packaging effort:
>> >
Hi Gurchetan,
> Thanks for the reminder. I did make a request to create the release
> tags, but changes were requested by Fedora packaging effort:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2242058
> https://bugzilla.redhat.com/show_bug.cgi?id=2241701
>
> So the request was canceled, but nev
Hi Gurchetan,
Gurchetan Singh writes:
> - As mentioned in v14:
> * AEMU: d6e6b99 "Delete VpxFrameParser.cpp"
> * gfxstream: 2131f78d Merge "gfxstream: add egl & gles deps.."
>
> are the proposed v.0.1.2 release points. If those commits are sufficient
> for packaging AEMU + gfxstream, le
Akihiko Odaki writes:
> Practically there is very low chance to hit the bug. I think only
> fuzzers and malicious actors will trigger it, and probably no one will
> dare using virtio-gpu-rutabaga or virtio-gpu-gl in a security-sensitive
> context.
Well, this is exactly what Chrome OS does, al
Gurchetan Singh writes:
> It's harder to get the attention of the Android build team than the Chrome
> build team. Though, there are a few issues with AEMU/gfxstream packaging
> we also need to figure out -- see "[PATCH v13 0/9] rutabaga_gfx +
> gfxstream" for details -- interested in your opini
Gurchetan Singh writes:
> On Fri, Aug 25, 2023 at 12:37 PM Alyssa Ross wrote:
>
>> Alyssa Ross writes:
>>
>> > Gurchetan Singh writes:
>> >
>> >> On Fri, Aug 25, 2023 at 12:11 AM Alyssa Ross wrote:
>> >>
>> >>> Gurc
Alyssa Ross writes:
> Gurchetan Singh writes:
>
>> On Fri, Aug 25, 2023 at 12:11 AM Alyssa Ross wrote:
>>
>>> Gurchetan Singh writes:
>>>
>>> > On Wed, Aug 23, 2023 at 4:07 AM Alyssa Ross wrote:
>>> >
>>> >> Gurch
Gurchetan Singh writes:
> On Fri, Aug 25, 2023 at 12:11 AM Alyssa Ross wrote:
>
>> Gurchetan Singh writes:
>>
>> > On Wed, Aug 23, 2023 at 4:07 AM Alyssa Ross wrote:
>> >
>> >> Gurchetan Singh writes:
>> >>
>> >> > -
Gurchetan Singh writes:
> On Wed, Aug 23, 2023 at 4:07 AM Alyssa Ross wrote:
>
>> Gurchetan Singh writes:
>>
>> > - Official "release commits" issued for rutabaga_gfx_ffi,
>> > gfxstream, aemu-base. For example, see crrev.com/c/4778941
>
Gurchetan Singh writes:
> - Official "release commits" issued for rutabaga_gfx_ffi,
> gfxstream, aemu-base. For example, see crrev.com/c/4778941
>
> - The release commits can make packaging easier, though once
> again all known users will likely just build from sources
> anyways
It's a sm
Gurchetan Singh writes:
> On Tue, Aug 1, 2023 at 8:18 AM Alyssa Ross wrote:
>
>> Gurchetan Singh writes:
>>
>> > On Mon, Jul 24, 2023 at 2:56 AM Alyssa Ross wrote:
>> >>
>> >> Gurchetan Singh writes:
>> >>
>> >
Gurchetan Singh writes:
> On Mon, Jul 24, 2023 at 2:56 AM Alyssa Ross wrote:
>>
>> Gurchetan Singh writes:
>>
>> > In terms of API stability/versioning/packaging, once this series is
>> > reviewed, the plan is to cut a "gfxstream upstream rele
Gurchetan Singh writes:
> +static int virtio_gpu_rutabaga_init(VirtIOGPU *g, Error **errp)
> +{
> +int result;
> +uint64_t capset_mask;
> +struct rutabaga_channels channels = { 0 };
> +struct rutabaga_builder builder = { 0 };
> +
> +VirtIOGPURutabaga *vr = VIRTIO_GPU_RUTABAGA(
Gurchetan Singh writes:
> +virtio-gpu rutabaga
> +---
> +
> +virtio-gpu can also leverage `rutabaga_gfx`_ to provide `gfxstream`_
> rendering
> +and `Wayland display passthrough`_. With the gfxstream rendering mode, GLES
> +and Vulkan calls are forwarded directly to the host wit
I was able to replicate my existing crosvm cross-domain testing setup
using QEMU, and all worked. I didn't test any other capsets.
Tested-by: Alyssa Ross
signature.asc
Description: PGP signature
Gurchetan Singh writes:
> In terms of API stability/versioning/packaging, once this series is
> reviewed, the plan is to cut a "gfxstream upstream release branch". We
> will have the same API guarantees as any other QEMU project then, i.e no
> breaking API changes for 5 years.
What about Rutaba
Linus Heckemann writes:
> Alyssa Ross writes:
>
>> Alyssa Ross writes:
>>
>>> Linus Heckemann writes:
>>>
>>>> While it's unclear to me what git send-email actually does with the
>>>> -v2 parameter (it is not documented, but
Alyssa Ross writes:
> Linus Heckemann writes:
>
>> While it's unclear to me what git send-email actually does with the
>> -v2 parameter (it is not documented, but also not rejected), it does
>> not add a v2 tag to the email's subject, which is what led to the
Linus Heckemann writes:
> While it's unclear to me what git send-email actually does with the
> -v2 parameter (it is not documented, but also not rejected), it does
> not add a v2 tag to the email's subject, which is what led to the
> mishap in [1].
>
> [1]: https://lists.nongnu.org/archive/html/
egins here:
<https://lore.kernel.org/qemu-devel/87sgd1ktx9@alyssa.is/>
Cc: Michael S. Tsirkin
Signed-off-by: Alyssa Ross
---
docs/interop/vhost-user.rst | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-use
ecisions based on the presence of gnutls,
rather than the gnutls option.
After making this change, I can successfully ./configure --disable-gnutls
on my system with gnutls installed, but not libtasn1.
Signed-off-by: Alyssa Ross
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This would previously give error messages like
> Received unexpected msg type.Expected 0 received 1
Signed-off-by: Alyssa Ross
---
hw/virtio/vhost-user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
index 29ea2b4
egins here:
<https://lore.kernel.org/qemu-devel/87sgd1ktx9@alyssa.is/>
Cc: Michael S. Tsirkin
Signed-off-by: Alyssa Ross
---
docs/interop/vhost-user.rst | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-use
egins here:
<https://lore.kernel.org/qemu-devel/87sgd1ktx9@alyssa.is/>
Cc: Michael S. Tsirkin
Signed-off-by: Alyssa Ross
---
docs/interop/vhost-user.rst | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-use
"Michael S. Tsirkin" writes:
> On Thu, Aug 06, 2020 at 08:59:09AM +, Alyssa Ross wrote:
>> "Michael S. Tsirkin" writes:
>>
>> > On Wed, Aug 05, 2020 at 03:13:06PM +, Alyssa Ross wrote:
>> >> Quoting from the definition of
"Michael S. Tsirkin" writes:
> On Wed, Aug 05, 2020 at 03:13:06PM +, Alyssa Ross wrote:
>> Quoting from the definition of VHOST_USER_SET_PROTOCOL_FEATURES in
>> vhost-user.rst:
>>
>> > Only legal if feature bit ``VHOST_USER_F
Quoting from the definition of VHOST_USER_SET_PROTOCOL_FEATURES in
vhost-user.rst:
> Only legal if feature bit ``VHOST_USER_F_PROTOCOL_FEATURES`` is present in
> ``VHOST_USER_GET_FEATURES``.
>
> .. Note::
>Slave that reported ``VHOST_USER_F_PROTOCOL_FEATURES`` must support
>this messa
Stefan Hajnoczi writes:
> On Fri, Jul 24, 2020 at 10:58:45AM +0000, Alyssa Ross wrote:
>> Alyssa Ross writes:
>>
>> > Stefan Hajnoczi writes:
>> >
>> >> On Tue, Jul 21, 2020 at 07:14:38AM +, Alyssa Ross wrote:
>> >>> Hi -- I h
Alyssa Ross writes:
> Stefan Hajnoczi writes:
>
>> On Tue, Jul 21, 2020 at 07:14:38AM +0000, Alyssa Ross wrote:
>>> Hi -- I hope it's okay me reaching out like this.
>>>
>>> I've been trying to test out the virtio-vhost-user implementation that
Stefan Hajnoczi writes:
> On Tue, Jul 21, 2020 at 07:14:38AM +0000, Alyssa Ross wrote:
>> Hi -- I hope it's okay me reaching out like this.
>>
>> I've been trying to test out the virtio-vhost-user implementation that's
>> been posted to this list a co
Stefan Hajnoczi writes:
> On Tue, Jul 21, 2020 at 07:14:38AM +0000, Alyssa Ross wrote:
>> Hi -- I hope it's okay me reaching out like this.
>>
>> I've been trying to test out the virtio-vhost-user implementation that's
>> been posted to this list a co
ic is
reproducible with two different kernels I tried (with different configs
and versions). I tried both versions of the virtio-vhost-user I was
able to find[1][2], and both exhibited the same behaviour.
Is this a known issue? Am I doing something wrong?
Thanks in advance -- I'm excitedly follo
38 matches
Mail list logo
