Hey,
This change adds an entry to the maintainers file to explicitly state
that any changes to vmware.c should be sent to the authors of the file
as well.
If you are thinking why do this now, off late we have seen quite a few
changes that touched the arch/x86/kernel/cpu/vmware.c file but were
On Sun, Aug 18, 2013 at 12:18:38PM +0300, Michael S. Tsirkin wrote:
On Sun, Aug 18, 2013 at 11:48:56AM +0300, Dan Aloni wrote:
On 3.10.7 and x86_64, as a result of sizeof(struct vhost_scsi) being
2152960 bytes the allocation failed once on my development machine.
Saw it would be prudent
On 09/04/2013 01:53 AM, Alok Kataria wrote:
Hey,
This change adds an entry to the maintainers file to explicitly state
that any changes to vmware.c should be sent to the authors of the file
as well.
If you are thinking why do this now, off late we have seen quite a few
changes that
On Mon, Sep 02, 2013 at 04:40:59PM +0800, Jason Wang wrote:
Currently, even if the packet length is smaller than VHOST_GOODCOPY_LEN, if
upend_idx != done_idx we still set zcopy_used to true and rollback this choice
later. This could be avoided by determining zerocopy once by checking all
On 22/08/13 23:02, Steven Rostedt wrote:
Please use a more specific name. bounce is too generic. I know
tracepoints are grouped by systems, but its easier for tools to just
state a tracepoint name than the system:event pair.
Sure, see my v2 patch coming soon.
Zoli
On Wed, Sep 04, 2013 at 09:18:40AM -0700, Sudeep Dutt wrote:
On Wed, 2013-08-21 at 10:51 -0700, Sudeep Dutt wrote:
ChangeLog:
=
v2 = v3:
a) Patch 1 data structure cleanups, header file include cleanups,
IDA interface reuse and switching to device_create_with_groups(..)
On Wed, 2013-08-21 at 10:51 -0700, Sudeep Dutt wrote:
ChangeLog:
=
v2 = v3:
a) Patch 1 data structure cleanups, header file include cleanups,
IDA interface reuse and switching to device_create_with_groups(..)
as per feedback from Greg Kroah-Hartman.
b) Patch 7 signal
On Wed, 2013-09-04 at 14:23 +0530, Alok Kataria wrote:
Hey,
This change adds an entry to the maintainers file to explicitly state
that any changes to vmware.c should be sent to the authors of the file
as well.
It never hurts to add MAINTAINER entries.
If you are thinking why do this now,
On 03/09/13 13:42, Konrad Rzeszutek Wilk wrote:
Correct. The double buffering code is being run in lib/swiotlb.c not the
xen-swiotlb.c. Hence the question of why not move the tracing in there.
I've put the trace to both locations before swiotlb_tbl_map_single is
called, so the same tracer will
Ftrace is currently not able to detect when SWIOTLB has to do double buffering.
Under Xen you can only see it indirectly in function_graph, when
xen_swiotlb_map_page() doesn't stop after range_straddles_page_boundary(), but
calls spinlock functions, memcpy() and xen_phys_to_bus() as well. This
On Wed, Sep 04, 2013 at 09:10:50PM +0100, Zoltan Kiss wrote:
On 03/09/13 13:42, Konrad Rzeszutek Wilk wrote:
Correct. The double buffering code is being run in lib/swiotlb.c not the
xen-swiotlb.c. Hence the question of why not move the tracing in there.
I've put the trace to both locations
On 09/04/2013 07:59 PM, Michael S. Tsirkin wrote:
On Mon, Sep 02, 2013 at 04:40:59PM +0800, Jason Wang wrote:
Currently, even if the packet length is smaller than VHOST_GOODCOPY_LEN, if
upend_idx != done_idx we still set zcopy_used to true and rollback this
choice
later. This could be
On Wed, 2013-09-04 at 10:16 -0700, Joe Perches wrote:
On Wed, 2013-09-04 at 14:23 +0530, Alok Kataria wrote:
Hey,
This change adds an entry to the maintainers file to explicitly state
that any changes to vmware.c should be sent to the authors of the file
as well.
It never hurts to
13 matches
Mail list logo
