From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: virtualization@lists.linux-foundation.org
Subject: [Q] guest identification and host runtime PM
Date: Thu, 9 Jan 2020 14:56:16 +0100 [thread overview]
Message-ID: <20200109135615.GA20339@ubuntu> (raw)
Hi,
I'm working on a VirtIO / vhost audio virtualisation solution [1,2]
and although it's already working rather well, some points still need
clarification.
1. Guest identification. Is there a standard way to identify guests in
a vhost driver? We need to send different audio topology to
different guests, therefore we need a way to reliably identify
them.
2. Runtime PM. Is there a standard or a preferred way to implement
runtime PM on the host side to guarantee that the device is always
powered on when guests need it and can be runtime suspended
otherwise?
Thanks
Guennadi
[1] https://github.com/thesofproject/sof-docs/pull/155
[2] https://github.com/thesofproject/linux/pull/1501
reply other threads:[~2020-01-09 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200109135615.GA20339@ubuntu \
--to=guennadi.liakhovetski@linux.intel.com \
--cc=virtualization@lists.linux-foundation.org \
/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.
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).