On Mon, Jun 6, 2022 at 7:05 PM Stefan Hajnoczi wrote:
>
> On Wed, Jun 01, 2022 at 09:10:58PM +0800, Yongji Xie wrote:
> > On Wed, Jun 1, 2022 at 9:03 PM Stefan Hajnoczi wrote:
> > >
> > > On Tue, May 31, 2022 at 05:52:21PM +0800, Xie Yongji wrote:
> > > > Currently we use 'id' option as the name
On Wed, Jun 01, 2022 at 09:10:58PM +0800, Yongji Xie wrote:
> On Wed, Jun 1, 2022 at 9:03 PM Stefan Hajnoczi wrote:
> >
> > On Tue, May 31, 2022 at 05:52:21PM +0800, Xie Yongji wrote:
> > > Currently we use 'id' option as the name of VDUSE device.
> > > It's a bit confusing since we use one value
On Wed, Jun 1, 2022 at 9:03 PM Stefan Hajnoczi wrote:
>
> On Tue, May 31, 2022 at 05:52:21PM +0800, Xie Yongji wrote:
> > Currently we use 'id' option as the name of VDUSE device.
> > It's a bit confusing since we use one value for two different
> > purposes: the ID to identfy the export within QE
On Tue, May 31, 2022 at 05:52:21PM +0800, Xie Yongji wrote:
> Currently we use 'id' option as the name of VDUSE device.
> It's a bit confusing since we use one value for two different
> purposes: the ID to identfy the export within QEMU (must be
> distinct from any other exports in the same QEMU pr
Currently we use 'id' option as the name of VDUSE device.
It's a bit confusing since we use one value for two different
purposes: the ID to identfy the export within QEMU (must be
distinct from any other exports in the same QEMU process, but
can overlap with names used by other processes), and the
