On Tue, Apr 10, 2018 at 10:52:52AM +0800, Jason Wang wrote:
> On 2018年04月02日 23:23, Tiwei Bie wrote:
> > This patch introduces a mdev (mediated device) based hardware
> > vhost backend. This backend is an abstraction of the various
> > hardware vhost accelerators (potentially any device that uses
On 2018年04月02日 23:23, Tiwei Bie wrote:
This patch introduces a mdev (mediated device) based hardware
vhost backend. This backend is an abstraction of the various
hardware vhost accelerators (potentially any device that uses
virtio ring can be used as a vhost accelerator). Some generic
mdev
The VIRTIO_BALLOON_F_PAGE_POISON feature bit is used to indicate if the
guest is using page poisoning. Guest writes to the poison_val config
field to tell host about the page poisoning value in use.
Signed-off-by: Wei Wang
Suggested-by: Michael S. Tsirkin
In some usages, e.g. virtio-balloon, a kernel module needs to know if
page poisoning is in use. This patch exposes the page_poisoning_enabled
function to kernel modules.
Signed-off-by: Wei Wang
Cc: Andrew Morton
Cc: Michal Hocko
This patch adds support to walk through the free page blocks in the
system and report them via a callback function. Some page blocks may
leave the free list after zone->lock is released, so it is the caller's
responsibility to either detect or prevent the use of such pages.
One use example of
On Mon, Apr 9, 2018 at 4:03 PM, Stephen Hemminger
wrote:
> On Mon, 9 Apr 2018 15:30:42 -0700
> Siwei Liu wrote:
>
>> On Mon, Apr 9, 2018 at 3:15 PM, Andrew Lunn wrote:
>> >> No, implementation wise I'd avoid changing the class on
On Mon, Apr 9, 2018 at 3:15 PM, Andrew Lunn wrote:
>> No, implementation wise I'd avoid changing the class on the fly. What
>> I'm looking to is a means to add a secondary class or class aliasing
>> mechanism for netdevs that allows mapping for a kernel device
>> namespace
On Fri, Apr 6, 2018 at 8:19 PM, Andrew Lunn wrote:
> Hi Siwei
>
>> I think everyone seems to agree not to fiddle with the ":" prefix, but
>> rather have a new class of network subsystem under /sys/class thus a
>> separate device namespace e.g. /sys/class/net-kernel for those
>>
On 03/22/2018 07:38 PM, Jason Wang wrote:
On 2018年03月22日 11:10, Michael S. Tsirkin wrote:
On Thu, Mar 22, 2018 at 09:52:18AM +0800, Jason Wang wrote:
On 2018年03月20日 12:26, Jonathan Helman wrote:
On Mar 19, 2018, at 7:31 PM, Jason Wang wrote:
On 2018年03月20日 06:14,
On 09/04/2018 20:58, Halil Pasic wrote:
> The driver has to be careful to expose the new \field{flags}
> value before checking if notifications are suppressed.
This paragraph should also be reworked to be part of the normative text
below, I think? The memory barrier must be "between two
This patch does three things. Emphasises that the example is pseudo-code
as we tend to stick to C otherwise and tweaks the wording, fixes
a typo in the pseudo code, and removes a line of code that I neither can
see the necessity for nor the sense of.
Signed-off-by: Halil Pasic
Occasionally we still use used and available ring instead of Device and
Driver Area respectively. Same goes for descriptor table with the
difference that depending on the context we need either Descriptor Area
or descriptor ring.
Let's clean these up, at least where the cleanup is trivial.
The subsection is talking about virtio buffers, that is possibly as
scatter-gather list mapped by multiple descriptors. Mistakenly we
at places we say descriptors instead of buffers.
While at it fix the title case capitalization. We seem to use
title case capitalization for subsections in most
The drivernormative was simply in the wrong place. It does not belong
to the code example.
Signed-off-by: Halil Pasic
---
packed-ring.tex |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/packed-ring.tex b/packed-ring.tex
index
There was a discrepancy between the pseudo code and the
textual description of the algorithm describing how shall
a driver supply buffers to the device.
The textual description did not make sense to me, so I've
changed that one to be more in sync with the pseudo code.
Signed-off-by: Halil Pasic
Some of these are more and some are less important. Please
be careful, there is always a chance that I misunderstood something
and that I'm trying to change for the worse.
I've identified some other weak point's too, but tried to
proceed in order the more grave and the better I think I
understand
On 4/9/2018 1:07 AM, Jiri Pirko wrote:
Sat, Apr 07, 2018 at 12:59:14AM CEST, sridhar.samudr...@intel.com wrote:
On 4/6/2018 5:48 AM, Jiri Pirko wrote:
Thu, Apr 05, 2018 at 11:08:22PM CEST, sridhar.samudr...@intel.com wrote:
[...]
+static int virtnet_bypass_join_child(struct net_device
Thank you Paolo
Avi
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Monday, 09 April, 2018 12:43 PM
> To: Avi Cohen (A); virtio-dev@lists.oasis-open.org
> Subject: Re: [virtio-dev] Dynamic assignment of vhost-user to a VM
>
> On 09/04/2018 08:33, Avi
On 04/09/2018 02:03 PM, Michael S. Tsirkin wrote:
On Fri, Apr 06, 2018 at 08:17:23PM +0800, Wei Wang wrote:
Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the
support of reporting hints of guest free pages to host via virtio-balloon.
Host requests the guest to report free
On 09/04/2018 08:33, Avi Cohen (A) wrote:
> Hello All,
> Is it possible to assign a vhost-user frontend to a VM *after* the VM was
> launched ?
> Best Regards
> Avi
If you're referring to QEMU then yes, you can dynamically create all of
character devices (to connect to the vhost-user server),
Hello All,
Is it possible to assign a vhost-user frontend to a VM *after* the VM was
launched ?
Best Regards
Avi
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail:
On Fri, Apr 06, 2018 at 08:17:23PM +0800, Wei Wang wrote:
> Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the
> support of reporting hints of guest free pages to host via virtio-balloon.
>
> Host requests the guest to report free page hints by sending a new cmd
> id to the
22 matches
Mail list logo