From: "hch@lst.de" <hch@lst.de>
To: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
Cc: "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"jroedel@suse.de" <jroedel@suse.de>,
"Raj, Ashok" <ashok.raj@intel.com>,
Will Deacon <will.deacon@arm.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
Robin Murphy <robin.murphy@arm.com>, "hch@lst.de" <hch@lst.de>,
"Lu, Baolu" <baolu.lu@intel.com>
Subject: Re: Device specific pass through in host systems - discuss user interface
Date: Sat, 8 Jun 2019 09:27:51 +0200 [thread overview]
Message-ID: <20190608072751.GA18928@lst.de> (raw)
In-Reply-To: <12f8c572074b7963705ba066fdde0f9fdf0bfc62.camel@intel.com>
Just curious, what exactly is the use case? Explaining how someone
would wan to use this should drive the way we design an interface for it.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-06-08 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 2:24 Device specific pass through in host systems - discuss user interface Prakhya, Sai Praneeth
2019-06-07 12:41 ` Robin Murphy
2019-06-08 1:44 ` Sai Praneeth Prakhya
2019-06-08 7:27 ` hch [this message]
2019-06-08 18:38 ` Sai Praneeth Prakhya
2019-06-09 3:20 ` Lu, Baolu
2019-06-10 5:41 ` Prakhya, Sai Praneeth
2019-06-10 13:56 ` Raj, Ashok
2019-06-11 4:38 ` Prakhya, Sai Praneeth
2019-06-11 4:56 ` Raj, Ashok
2019-06-11 17:27 ` Prakhya, Sai Praneeth
2019-07-01 8:59 ` jroedel
2019-07-03 2:01 ` Prakhya, Sai Praneeth
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=20190608072751.GA18928@lst.de \
--to=hch@lst.de \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=robin.murphy@arm.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.