Hi Stefan,
> >> We need a device ID for virtio-pmem devices. As 24 is already
> >> requested by virtio-mem, so requesting next available(25)
> >>
> >> Signed-off-by: Pankaj Gupta
> >> ---
> >> content.tex | 2 ++
> >> 1 file changed, 2 insertions(+)
> >
> > virtio-mem is designed for hotplug.
On 5/22/2018 9:12 AM, Jiri Pirko wrote:
Fixing the subj, sorry about that.
Tue, May 22, 2018 at 05:46:21PM CEST, m...@redhat.com wrote:
On Tue, May 22, 2018 at 05:36:14PM +0200, Jiri Pirko wrote:
Tue, May 22, 2018 at 05:28:42PM CEST, sridhar.samudr...@intel.com wrote:
On 5/22/2018 2:08 AM,
On 05/22/18 21:11, Christoffer Dall wrote:
> Only the device updates the used ring.
>
> This looks like a typo as a result of copy-paste from the description of
> the Available Ring.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/12
> Signed-off-by: Christoffer Dall
> ---
> split-ri
On Tue, May 22, 2018 at 07:38:44PM +0200, Jiri Pirko wrote:
> >> >> In private
> >> >> flag. I don't see no reason to break this pattern here.
> >> >
> >> >Other masters are setup from userspace, this one is set up automatically
> >> >by kernel. So the bar is higher, we need an interface that exist
Only the device updates the used ring.
This looks like a typo as a result of copy-paste from the description of
the Available Ring.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/12
Signed-off-by: Christoffer Dall
---
split-ring.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, May 22, 2018 at 05:45:01PM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 05:32:30PM CEST, m...@redhat.com wrote:
> >On Tue, May 22, 2018 at 05:13:43PM +0200, Jiri Pirko wrote:
> >> Tue, May 22, 2018 at 03:39:33PM CEST, m...@redhat.com wrote:
> >> >On Tue, May 22, 2018 at 03:26:26PM +0200,
On Tue, May 22, 2018 at 05:36:14PM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 05:28:42PM CEST, sridhar.samudr...@intel.com wrote:
> >
> >On 5/22/2018 2:08 AM, Jiri Pirko wrote:
> >> Tue, May 22, 2018 at 11:06:37AM CEST, j...@resnulli.us wrote:
> >> > Tue, May 22, 2018 at 04:06:18AM CEST, sridh
On Tue, May 22, 2018 at 05:13:43PM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 03:39:33PM CEST, m...@redhat.com wrote:
> >On Tue, May 22, 2018 at 03:26:26PM +0200, Jiri Pirko wrote:
> >> Tue, May 22, 2018 at 03:17:37PM CEST, m...@redhat.com wrote:
> >> >On Tue, May 22, 2018 at 03:14:22PM +0200,
On 5/22/2018 2:08 AM, Jiri Pirko wrote:
Tue, May 22, 2018 at 11:06:37AM CEST, j...@resnulli.us wrote:
Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudr...@intel.com wrote:
Use the registration/notification framework supported by the generic
failover infrastructure.
Signed-off-by: Sridhar S
On 2018-05-22 11:03:37 +0100, Stefan Hajnoczi wrote:
> On Fri, May 18, 2018 at 04:43:36PM -0500, Venu Busireddy wrote:
> > On 2018-05-18 17:06:23 +0100, Stefan Hajnoczi wrote:
> > > On Thu, May 17, 2018 at 09:06:04AM -0400, Venu Busireddy wrote:
> > >
> > > Can you describe a use case where vendor
On Tue, May 22, 2018 at 03:26:26PM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 03:17:37PM CEST, m...@redhat.com wrote:
> >On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote:
> >> Tue, May 22, 2018 at 03:12:40PM CEST, m...@redhat.com wrote:
> >> >On Tue, May 22, 2018 at 11:08:53AM +0200,
On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 03:12:40PM CEST, m...@redhat.com wrote:
> >On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote:
> >> Tue, May 22, 2018 at 11:06:37AM CEST, j...@resnulli.us wrote:
> >> >Tue, May 22, 2018 at 04:06:18AM CEST, sr
On 22.05.2018 11:42, Stefan Hajnoczi wrote:
> On Fri, May 18, 2018 at 10:11:06AM +0530, Pankaj Gupta wrote:
>> We need a device ID for virtio-pmem devices. As 24 is already
>> requested by virtio-mem, so requesting next available(25)
>>
>> Signed-off-by: Pankaj Gupta
>> ---
>> content.tex | 2 ++
On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote:
> Tue, May 22, 2018 at 11:06:37AM CEST, j...@resnulli.us wrote:
> >Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudr...@intel.com wrote:
> >>Use the registration/notification framework supported by the generic
> >>failover infrastructur
On Fri, May 18, 2018 at 04:43:36PM -0500, Venu Busireddy wrote:
> On 2018-05-18 17:06:23 +0100, Stefan Hajnoczi wrote:
> > On Thu, May 17, 2018 at 09:06:04AM -0400, Venu Busireddy wrote:
> >
> > Can you describe a use case where vendor-specific extensions make sense
> > as opposed to extending the
On Fri, May 18, 2018 at 10:11:06AM +0530, Pankaj Gupta wrote:
> We need a device ID for virtio-pmem devices. As 24 is already
> requested by virtio-mem, so requesting next available(25)
>
> Signed-off-by: Pankaj Gupta
> ---
> content.tex | 2 ++
> 1 file changed, 2 insertions(+)
virtio-mem is
On Tue, 22 May 2018 18:26:15 +0800
Tiwei Bie wrote:
> Allocate a feature bit for virtio devices which support SR-IOV.
>
> Suggested-by: Michael S. Tsirkin
> Signed-off-by: Tiwei Bie
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/11
Reviewed-by: Cornelia Huck
--
Allocate a feature bit for virtio devices which support SR-IOV.
Suggested-by: Michael S. Tsirkin
Signed-off-by: Tiwei Bie
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/11
---
More details can be found from this thread:
https://patchwork.kernel.org/patch/10285541/
This patch needs below
On Tue, May 22, 2018 at 11:56:12AM +0200, Cornelia Huck wrote:
> On Tue, 22 May 2018 12:56:23 +0800
> Tiwei Bie wrote:
>
> > Allocate a feature bit for virtio devices which support SR-IOV.
> >
> > Suggested-by: Michael S. Tsirkin
> > Signed-off-by: Tiwei Bie
> > Fixes: https://github.com/oasis
On Tue, 22 May 2018 12:56:23 +0800
Tiwei Bie wrote:
> Allocate a feature bit for virtio devices which support SR-IOV.
>
> Suggested-by: Michael S. Tsirkin
> Signed-off-by: Tiwei Bie
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/11
> ---
> More details can be found from this thread:
20 matches
Mail list logo
