On Fri, 2015-06-26 at 18:51 +0300, Dan Carpenter wrote:
> It's based on earlier patches on the list.
>
> Normally only Greg tests that patches apply and it will for him
> because
> he applies them as the order they arrive. But we should probably
> start
> putting notes on the patches which earlie
cn_msg should be validated instead of msg after memory allocation.
Signed-off-by: Maninder Singh
Reviewed-by: Akhilesh Kumar
---
drivers/hv/hv_utils_transport.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hv/hv_utils_transport.c b/drivers/hv/hv_utils_transport
>> >Yeah. You're right. Doing a vmalloc() when kmalloc() doesn't have even
>> >a tiny sliver of RAM isn't going to work. It's easier to use
>> >libcfs_kvzalloc() everywhere, but it's probably the wrong thing.
>>
>> The original reason we have the vmalloc water mark wasn't so much the
>> issue
When packet encapsulation is in use, the MTU needs to be reduced for
headroom reservation.
The existing code takes the updated MTU value only from the host side.
But vSwitch extensions, such as Open vSwitch, require the flexibility
to change the MTU to different values from within a guest during th
On 07/01/2015 04:02 AM, Gioh Kim wrote:
This patch enables debugfs file /sys/kernel/debug/ion/heaps/system_shrink
Nit: This technically enables debugfs shrinking for all heaps, not just
the system heap although the system heap is the only one with a shrinker
right now.
to shrink pool and get
On 07/01/2015 04:02 AM, Gioh Kim wrote:
This patch shrink page-pool by page unit.
The system shrinker calls ion_heap_shrink_count() to get nr_to_scan,
and pass it to ion_heap_shrink_scan().
The problem is the return value of ion_heap_shrink_count() is the number
of pages but ion_system_heap_shri
On Wed, 2015-07-01 at 23:20 -0700, Joe Perches wrote:
> On Wed, 2015-07-01 at 09:59 +0200, Krzysztof Hałasa wrote:
> > Mario Bambagini writes:
> >
> > > Defines have been written in more than one line to match the 80-character
> > > rule. This error has been fixed 6 times in this file.
> > > The
Also changes vme_bus_error_handler to take generic address modifier code
instead of raw contents of a device-specific attribute register.
Signed-off-by: Dmitry Kalinkin
Cc: Igor Alekseev
---
drivers/vme/bridges/vme_tsi148.c | 4 ++-
drivers/vme/vme.c| 61 +++
The current VME bus error handler adds errors to the bridge error list.
vme_master_{read,write} then traverses that list to look for relevant
errors.
Such scheme didn't work well for accesses going through vme_master_mmap
because they would also allocate a vme_bus_error, but have no way to do
vme_
Error handling code found in tsi148 is not device specific. In fact it
already relies on shared vme_bus_error struct and vme_bridge.vme_errors
field. The other bridge driver could reuse this code if it is shared.
This introduces a slight behavior change: vme error message won't be
triggered in a r
This moves tsi148 error handling into VME subsystem so it can be shared with
the other bridge driver. Then there is a change to close a fixme on separating
errors by address space. And finally a fix for memory leak problem that was
introduced with support of mmap's.
The next logical step in thi
"Denis V. Lunev" writes:
> From: Andrey Smetanin
>
> Hypervisor Top Level Functional Specification v3.1/4.0 notes that cpuid
> (0x4003) EDX's 10th bit should be used to check that Hyper-V guest
> crash MSR's functionality available.
>
> This patch should fix this recognition. Currently the c
From: Andrey Smetanin
Hypervisor Top Level Functional Specification v3.1/4.0 notes that cpuid
(0x4003) EDX's 10th bit should be used to check that Hyper-V guest
crash MSR's functionality available.
This patch should fix this recognition. Currently the code checks EAX
register instead of EDX.
13 matches
Mail list logo
