From: Alyssa Ross <hi@alyssa.is>
To: Dom Rodriguez <shymega@shymega.org.uk>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH v2] crosvm: Rename `--vhost-user-{fs,gpu}` args
Date: Mon, 21 Oct 2024 21:53:54 +0200 [thread overview]
Message-ID: <87y12htep9.fsf@alyssa.is> (raw)
In-Reply-To: <875xpl962r.fsf@alyssa.is>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Alyssa Ross <hi@alyssa.is> writes:
> Dom Rodriguez <shymega@shymega.org.uk> writes:
>
>> On 28.09.2024 16:27, Alyssa Ross wrote:
>>>
>>>You're right! I've just spent the last little while looking around
>>>trying to figure out what's up here, and I think I've figured it out.
>>>
>>>In this commit[1] they made the vhost-user-fs tag optional, because it
>>>can now be set with virtiosfd instead of the VMM. This is probably
>>>good, because the more generic vhost-user becomes, the more hope
>>>Spectrum has of one day not needing Cloud Hypervisor patches. :) So we
>>>could try using --vhost-user fs for crosvm, and then passing --tag to
>>>virtiofsd, but it'd need to be tested with VMM=qemu and
>>>VMM=cloud-hypervisor as well, because I'm not sure whether they support
>>>a backend-provided tag.
>>
>> Oh, that explains *a lot*! I agree, a generic approach would be
>> preferable.
>>
>>>If that's too much work, I'd also be happy to apply just the GPU part of
>>>this patch. Just let me know. :)
>>
>> I've started a new job, and so I've only really got weekends free - and
>> even then, I have Repair Cafes to volunteer at.
>>
>> If I send over the GPU patch only, can you apply that, and then we can
>> discuss on Matrix/IRC the best approach for `vhost-user-fs`? Feel free
>> to tag me - I'm mostly using IRC rightn ow.
>
> SGTM.
BTW: I've just seen this when building release/checks/wayland after
a recent Nixpkgs update:
machine # [ 18.830327] crosvm[987]: [src/crosvm/cmdline.rs:2829] Deprecated disk flags such as --[rw]disk or --[rw]root are passed. Use --block instead.
Just in case you're interested. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2024-10-21 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 22:42 [PATCH v2] crosvm: Rename `--vhost-user-{fs,gpu}` args Dom Rodriguez
2024-09-07 16:40 ` Alyssa Ross
2024-09-21 22:52 ` Dom Rodriguez
2024-09-28 14:27 ` Alyssa Ross
2024-10-18 19:53 ` Dom Rodriguez
2024-10-21 9:08 ` Alyssa Ross
2024-10-21 19:53 ` Alyssa Ross [this message]
2024-11-09 1:03 ` Dom RODRIGUEZ
2024-11-09 21:46 ` Alyssa Ross
2024-11-11 1:35 ` Dom Rodriguez
2024-11-11 10:49 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y12htep9.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.org \
--cc=shymega@shymega.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).