Hello.
Currently the link status auto-negotiation is enabled
for any SGMII link with fixed-link DT binding.
The regression was reported:
https://lkml.org/lkml/2015/7/8/865
Apparently not all HW that implements SGMII protocol, generates the
inband status for the auto-negotiation to work.
More detai
On 07/15/2015 09:16 PM, Ming Lei wrote:
Hi,
This patches kills two kinds of atomic operations in block
accounting I/O.
The 1st two patches convert atomic refcount of partition
into percpu refcount.
The 2nd two patches converts partition->in_flight[] into percpu
variable.
With this change, ~15
Takashi Iwai writes:
> Great, I queued the patch now. It'll be included in the next pull
> request for 4.2-rc3.
Thanks -- you're an awesome maintainer.
--
-keith
signature.asc
Description: PGP signature
Currently fixed_phy driver recognizes only the link-up state.
This simple patch adds an implementation of link-down state.
It fixes the status registers when link is down, and also allows
to register the fixed-phy with link down without specifying the speed.
Signed-off-by: Stas Sergeev
CC: Flor
Currently the PHY management type is selected by the MAC driver arbitrary.
The decision is based on the presence of the "fixed-link" node and on a
will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started
to use the in-band status for auto-negotiation on
On 07/16/2015 01:46 AM, Peter Zijlstra wrote:
On Wed, Jul 15, 2015 at 10:01:02PM -0400, Waiman Long wrote:
On 07/15/2015 05:39 AM, Peter Zijlstra wrote:
On Tue, Jul 14, 2015 at 10:13:35PM -0400, Waiman Long wrote:
Frequent CPU halting (vmexit) and CPU kicking (vmenter) lengthens
critical secti
The commit 898b2970e2c9 ("mvneta: implement SGMII-based in-band link state
signaling") implemented the link parameters auto-negotiation unconditionally.
Unfortunately it appears that some HW that implements SGMII protocol,
doesn't generate the inband status, so it is not possible to auto-negotiate
Hi Stefano,
On 16/07/2015 16:19, Stefano Stabellini wrote:
diff --git a/include/xen/page.h b/include/xen/page.h
index c5ed20b..8ebd37b 100644
--- a/include/xen/page.h
+++ b/include/xen/page.h
@@ -1,11 +1,30 @@
#ifndef _XEN_PAGE_H
#define _XEN_PAGE_H
+#include
+
+/* The hypercall interface
Hi Stefano,
On 16/07/2015 16:23, Stefano Stabellini wrote:
diff --git a/include/xen/page.h b/include/xen/page.h
index 8ebd37b..b1f7722 100644
--- a/include/xen/page.h
+++ b/include/xen/page.h
@@ -39,4 +39,24 @@ struct xen_memory_region
xen_extra_mem[XEN_EXTRA_MEM_MAX_REGIONS];
extern unsigne
On Sun, Jul 12, 2015 at 9:54 AM, Calvin Owens wrote:
> These objects can be referenced concurrently throughout the driver, we
> need a way to make sure threads can't delete them out from under each
> other. This patch adds the refcount, and refactors the code to use it.
>
> Additionally, we cannot
On Jul 16, 2015, at 11:24 PM, Steven Rostedt wrote:
Hi, Steve
> On Thu, 16 Jul 2015 22:29:05 +0900
> Jungseok Lee wrote:
[ snip ]
>> The data looks odd in two points.
>> 1) the number of entry
>> There is a mismatch between start token and real data
>
> Yep, good catch. As soon as I read that
On Thu, 9 Jul 2015, Julien Grall wrote:
> Currently, a grant is always based on the Xen page granularity (i.e
> 4KB). When Linux is using a different page granularity, a single page
> will be split between multiple grants.
>
> The new helpers will be in charge to split the Linux page into grant an
On 07/16/2015 08:59 AM, Tejun Heo wrote:
On Thu, Jul 16, 2015 at 08:48:41AM -0600, Jens Axboe wrote:
I've played with this before, but always ran into the hurdle of making
part_in_flight() too expensive ended up hurting results in the end. Making
the inc/dec parts of accounting percpu is a no-br
On Thu, Jul 16, 2015 at 10:48 PM, Jens Axboe wrote:
> On 07/15/2015 09:16 PM, Ming Lei wrote:
>>
>> Hi,
>>
>> This patches kills two kinds of atomic operations in block
>> accounting I/O.
>>
>> The 1st two patches convert atomic refcount of partition
>> into percpu refcount.
>>
>> The 2nd two patc
On 07/16/2015 10:07 AM, Waiman Long wrote:
On 07/16/2015 01:42 AM, Peter Zijlstra wrote:
On Wed, Jul 15, 2015 at 08:18:23PM -0400, Waiman Long wrote:
On 07/15/2015 05:10 AM, Peter Zijlstra wrote:
/*
+ * A failed cmpxchg doesn't provide any memory-ordering
guarantees,
+ * so we
On Thu, Jul 16, 2015 at 08:48:41AM -0600, Jens Axboe wrote:
> I've played with this before, but always ran into the hurdle of making
> part_in_flight() too expensive ended up hurting results in the end. Making
> the inc/dec parts of accounting percpu is a no-brainer, unfortunately the
> summing the
On Thu, Jul 16, 2015 at 04:15:16PM +0200, Paul Bolle wrote:
> Let's put it this was. If one does
> sudo find /sys -perm -o=r -name uevent -exec grep -H MODALIAS=platform:
> {} \;
>
> or
> sudo find /sys -perm -o=r -name modalias -exec grep -H platform: {} \;
> (both lists should be simi
Jens Axboe writes:
> Lots of devices support huge discard sizes these days. Depending
> on how the device handles them internally, huge discards can
> introduce massive latencies (hundreds of msec) on the device side.
>
> We have a sysfs file, discard_max_bytes, that advertises the max
> hardware
On Thu, 9 Jul 2015, Julien Grall wrote:
> Many PV drivers contain the idiom:
>
> pfn = page_to_mfn(...) /* Or similar */
> gnttab_grant_foreign_access_ref
>
> Replace it by a new helper. Note that when Linux is using a different
> page granularity than Xen, the helper only gives access to the fir
On 7/16/2015 6:59 AM, Seth Forshee wrote:
> On Wed, Jul 15, 2015 at 10:15:21PM -0500, Eric W. Biederman wrote:
>> Seth I think for the LSMs we should start with:
>>
>> diff --git a/security/security.c b/security/security.c
>> index 062f3c997fdc..5b6ece92a8e5 100644
>> --- a/security/security.c
>> +
On 07/16/2015 09:01 AM, Ming Lei wrote:
On Thu, Jul 16, 2015 at 10:48 PM, Jens Axboe wrote:
On 07/15/2015 09:16 PM, Ming Lei wrote:
Hi,
This patches kills two kinds of atomic operations in block
accounting I/O.
The 1st two patches convert atomic refcount of partition
into percpu refcount.
On Thu, Jul 16, 2015 at 04:04:30PM +0100, Waiman Long wrote:
> On 07/16/2015 10:07 AM, Waiman Long wrote:
> > On 07/16/2015 01:42 AM, Peter Zijlstra wrote:
> >> On Wed, Jul 15, 2015 at 08:18:23PM -0400, Waiman Long wrote:
> >>> On 07/15/2015 05:10 AM, Peter Zijlstra wrote:
> /*
> +
On Thu, Jul 16, 2015 at 03:14:55PM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2015-07-16 at 15:03 +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2015-07-16 at 12:00 +1000, Michael Ellerman wrote:
> > > That would fix the problem with smp_mb__after_unlock_lock(), but not
> > > the original wor
Fixed up some checkpatch.pl style issues.
Line greater than 80 Chars in multiple locations.
Signed-off-by: Craig Inches
---
drivers/staging/dgnc/dgnc_tty.c | 168 ++--
1 file changed, 110 insertions(+), 58 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_t
On 07/16/2015 09:07 AM, Jeff Moyer wrote:
Jens Axboe writes:
Lots of devices support huge discard sizes these days. Depending
on how the device handles them internally, huge discards can
introduce massive latencies (hundreds of msec) on the device side.
We have a sysfs file, discard_max_bytes
On Thu, 9 Jul 2015, Julien Grall wrote:
> All the usage of the field pfn are done using the same idiom:
>
> pfn_to_page(grant->pfn)
>
> This will return always the same page. Store directly the page in the
> grant to clean up the code.
>
> Signed-off-by: Julien Grall
> Cc: Konrad Rzeszutek Wil
Hello,
The patchset adds support for 4 wire touchscreen on Toradex Colibri
VF50 modules. Patches are based on top of shawn's branch.
Changes since v1:
1. Fix/drop comments
2. Use an inline function for multiple gpiod_get calls in probe
3. Remove the pull up in the pinmux specified in DT for touch
The Colibri Vybrid VF50 module supports 4-wire touchscreens using
FETs and ADC inputs. This driver uses the IIO consumer interface
and relies on the vf610_adc driver based on the IIO framework.
Signed-off-by: Sanchayan Maity
---
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/
This adds device tree binding documentation for the Colibri VF50
touchscreen driver.
Signed-off-by: Sanchayan Maity
---
.../bindings/input/touchscreen/colibri-vf50-ts.txt | 34 ++
1 file changed, 34 insertions(+)
create mode 100644
Documentation/devicetree/bindings/input/to
Add device tree node for touchscreen support on Colibri VF50. The
touchscreen functionality on VF50 uses the ADC channels of Vybrid
and some GPIOs. Also add pinctrl nodes for proper pinmux.
Signed-off-by: Sanchayan Maity
---
arch/arm/boot/dts/vf500-colibri-eval-v3.dts | 4 +++
arch/arm/boot/dts
This commit adds io-channel-cells property to the ADC node. This
property is required in order for an IIO consumer driver to work.
Especially required for Colibri VF50, as the touchscreen driver
uses ADC channels with the ADC driver based on IIO framework.
Signed-off-by: Sanchayan Maity
---
arch
Hi Chaotian,
On Thu, Jul 16, 2015 at 7:36 PM, Chaotian Jing
wrote:
> From: Eddie Huang
>
> Add node mmc0 ~ mmc3 for mt8173.dtsi
> Add node mmc0, mmc1 for mt8173-evb.dts
>
> Signed-off-by: Chaotian Jing
> Signed-off-by: Eddie Huang
> ---
> Remove clk_null
> Base on 4.2-rc1, and
> https://gith
On Tue, Jul 14, 2015 at 02:48:53PM -0600, Alex Williamson wrote:
> This continues the attempt to fix commit fb170fb4c548 ("iommu/vt-d:
> Introduce helper functions to make code symmetric for readability").
> The previous attempt in commit 71684406905f ("iommu/vt-d: Detach
> domain *only* from attac
On Thu, Jul 16, 2015 at 3:17 PM, YH Huang wrote:
> On Thu, 2015-07-16 at 14:54 +0800, Daniel Kurtz wrote:
>> On Thu, Jul 16, 2015 at 1:38 PM, YH Huang wrote:
>> > On Wed, 2015-07-15 at 23:59 +0800, YH Huang wrote:
>> >> On Mon, 2015-07-13 at 18:19 +0800, Daniel Kurtz wrote:
>> >> > On Mon, Jul 13
On 2015/7/16 22:19, Paul Bolle wrote:
> Hi,
>
> On do, 2015-07-16 at 19:59 +0800, zhengxing wrote:
>> I mean that the use of MODALIAS() in this patch, and I refered to
>> tegra_max98090.c(have been upstreamed) that used it like this also. So
>> I didn't care the using.
>
> And I think the same pr
Hi all,
in order to be able to use Micron Quad SPI memories with the new Atmel QSPI
controller I added a new set_protocol() callback into struct spi_nor.
Indeed, once the quad I/O mode has been enabled on a Micron QSPI flash by
clearing bit 7 in its Enhanced Volatile Configuration Register, this m
Depending on the SPI clock frequency, the Fast Read op code and the
Single/Dual Data Rate mode, the number of dummy cycles can be tuned to
improve transfer speed.
The actual number of dummy cycles is specific for each memory model and is
provided by the manufacturer thanks to the memory datasheet.
This driver add support to the new Atmel QSPI controller embedded into
sama5d2x SoCs. It expects a NOR memory to be connected to the QSPI
controller.
Signed-off-by: Cyrille Pitchen
---
drivers/mtd/spi-nor/Kconfig | 7 +
drivers/mtd/spi-nor/Makefile| 1 +
drivers/mtd/spi-nor/a
Hi,
On 07/16/2015 01:57 AM, Paul Walmsley wrote:
> On Wed, 15 Jul 2015, Paul Walmsley wrote:
>
>> On Wed, 3 Jun 2015, Vignesh R wrote:
>>
>>> Legacy IPs like PWMSS, present under l4per2_7xx_clkdm, cannot support
>>> smart-idle when its clock domain is in HW_AUTO on DRA7 SoCs. Hence,
>>> program c
Both the SPI controller and the flash memory must agree on the number of
dummy cycles to use for Fast Read commands. For Spansion memories, this
number of dummy cycles is configured through a so called latency code in
their Control Register.
The right latency code can be found in the memory datashe
Both the SPI controller and the NOR flash memory need to agree on the
number of dummy cycles to use for Fast Read commands. For Spansion
memories, this number of dummy cycles is not given directly but through a
so called "latency code".
The latency code can be found into the memory datasheet and de
This patch documents the DT bindings for the driver of the Atmel QSPI
controller embedded inside sama5d2x SoCs.
Signed-off-by: Cyrille Pitchen
---
.../devicetree/bindings/mtd/atmel-quadspi.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/de
Hi,
On 05/07/2015 at 23:48:26 +0200, Thomas Gleixner wrote :
> On Fri, 3 Jul 2015, David Dueck wrote:
>
> > This fixes a warning when using RT-Preempt.
>
> That's not a proper explanation for the patch and by all means it
> cannot fix anything because free_irq() is just a different wrapper
> aro
The number of dummy cycles used during Fast Read commands can be reduced
to improve transfer performances. Each manufacturer has a dedicated set of
registers to provide the memory with the exact number of dummy cycles it
should expect. Both the memory and the (Q)SPI controller must agree on
this nu
On 07/15/2015 07:37 PM, Catalin Marinas wrote:
> Ok, so simply taking the call out of the loop won't work unless we
> conditionally define these functions (wouldn't be too bad since we have
> some #if CONFIG_PGTABLE_LEVELS already introduced by this patch but it
> would be nicer without).
>
> Anyw
Once the Quad SPI mode has been enabled on a Micron flash memory, this
device expects ALL the following commands to use the SPI 4-4-4 protocol.
The (Q)SPI controller needs to be notified about the protocol change so it
can adapt and keep on dialoging with the Micron memory.
Signed-off-by: Cyrille
On Thu, 2015-07-16 at 23:11 +, Craig Inches wrote:
> Fixed up some checkpatch.pl style issues.
> Line greater than 80 Chars in multiple locations.
I think most all of these are not improvements.
Please use --strict when verifying your patches.
Please fix the time on your system.
--
To unsubs
On Fri, 17 Jul 2015 00:01:25 +0900
Jungseok Lee wrote:
> I've gathered stack tracer data with your update.
>
> 1) stack_trace
> DepthSize Location(35 entries)
> -
> 0) 4424 16 put_cpu_partial+0x28/0x1d0
> 1) 4408 80 get_p
Hi,
On 07/16/2015 03:24 AM, Paul Walmsley wrote:
> Hi,
>
> some comments.
>
> On Wed, 3 Jun 2015, Vignesh R wrote:
>
>> Add hwmod entries for the PWMSS on DRA7.
>>
>> Set l4_root_clk_div as the main_clk of PWMSS. It is fixed-factored clock
>> equal to L4PER2_L3_GICLK/2(l3_iclk_div/2).
>> As per
Including an asm/ header directly is best avoided, so use linux/atomic.h
instead of asm/cmpxchg.h in linux/llist.h.
Signed-off-by: Will Deacon
---
include/linux/llist.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/llist.h b/include/linux/llist.h
index fbf10a0
The qrwlock implementation is slightly heavy in its use of memory
barriers, mainly through the use of cmpxchg and _return atomics, which
imply full barrier semantics.
This patch modifies the qrwlock code to use the more relaxed atomic
routines so that we can reduce the unnecessary barrier overhead
Hi all,
This is version two of the patches I previously posted here:
https://lwn.net/Articles/650862/
The series adds support for a family of relaxed atomics to the kernel.
More specifically:
- acquire/release/relaxed flavours of xchg, cmpxchg and {add,sub}_return
- atomic_read_acquire
By defining our SMP atomics in terms of relaxed operations, we gain
a small reduction in code size and have acquire/release/fence variants
generated automatically by the core code.
Signed-off-by: Will Deacon
---
arch/arm/include/asm/atomic.h | 37 ++---
arch/arm/incl
On Fri, 10 Jul 2015, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 09, 2015 at 09:42:21PM +0100, Julien Grall wrote:
> > When Linux is using 64K page granularity, every page will be slipt in
> > multiple non-contiguous 4K MFN (page granularity of Xen).
>
> But you don't care about that on the Linux l
We can use some (admittedly ugly) macros to generate the 32-bit and
64-bit based atomic_long implementations from the same code.
Signed-off-by: Will Deacon
---
include/asm-generic/atomic-long.h | 189 --
1 file changed, 40 insertions(+), 149 deletions(-)
diff
cmpxchg64_relaxed is now defined by asm-generic/atomic.h, so we can
remove our local definition from the lockref code.
Signed-off-by: Will Deacon
---
lib/lockref.c | 8
1 file changed, 8 deletions(-)
diff --git a/lib/lockref.c b/lib/lockref.c
index 494994bf17c8..5a92189ad711 100644
---
Whilst porting the generic qrwlock code over to arm64, it became
apparent that any portable locking code needs finer-grained control of
the memory-ordering guarantees provided by our atomic routines.
In particular: xchg, cmpxchg, {add,sub}_return are often used in
situations where full barrier sem
This patch adds atomic_long_t wrappers for the new relaxed atomic
operations.
Signed-off-by: Will Deacon
---
include/asm-generic/atomic-long.h | 86 +++
1 file changed, 59 insertions(+), 27 deletions(-)
diff --git a/include/asm-generic/atomic-long.h
b/includ
On Thu, 2015-07-16 at 16:25 +0530, Viresh Kumar wrote:
> Hi Andy/Joe,
>
> I got a warning today for my cover-letter, and it looked like a false
> positive. Please have a look, based of v4.2-rc2.
> ---
> -cover-letter.patch
> ---
> WARNING: Possible unwra
> Whenever the UART device driver gets closed from userland, the driver
> disables the UART unit and then stops its clock to save power.
>
> The bit which disabled the UART unit is described as:
>
> "UART Enable. If this bit is set to 1, the UART is enabled. Data
> transmission and reception oc
Separate the functionality using sequences of register writes from the
functions that take register defaults. This change renames the arguments
in order to support the extension of reg_sequence to take an optional
delay to be applied after any given register in a sequence is written.
This avoids ad
Add an optional delay_us field in reg_sequence to allow the client to
specify a delay (in microseconds) to be applied after any given write
in a sequence of writes.
We treat a delay in a sequence the same way we treat a page change as
they are logically similar in that you can coalesce all write b
Hi Guys,
There are about 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
-
It doesn't make sense to enable merge because the I/O
submitted to backing file is handled page by page.
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index f7a4c9d..e4381f8 100644
--- a/driv
The following patch will use dio/aio to submit IO to backing file,
then it needn't to schedule IO concurrently from work, so
use kthread_work for decreasing context switch cost a lot.
For non-AIO case, single thread has been used for long long time,
and it was just converted to work in v4.0, which
The top-level Makefile re-routes all %docs targets to the Documentation
makefiles. The DocBook makefile supports a lot more targets than the kdbus
makefile, and it seems unreasonable to expect that both will always be in
sync.
Therefore, add a fallback no-op target %docs: which is used for all
uns
On Thu, 9 Jul 2015, Julien Grall wrote:
> All the ring (xenstore, and PV rings) are always based on the page
> granularity of Xen.
>
> Signed-off-by: Julien Grall
> Cc: Konrad Rzeszutek Wilk
> Cc: Boris Ostrovsky
> Cc: David Vrabel
Reviewed-by: Stefano Stabellini
> Changes in v2:
>
On Thu, 9 Jul 2015, Julien Grall wrote:
> The console ring is always based on the page granularity of Xen.
>
> Signed-off-by: Julien Grall
> Cc: Greg Kroah-Hartman
> Cc: Jiri Slaby
> Cc: David Vrabel
> Cc: Stefano Stabellini
> Cc: Boris Ostrovsky
> Cc: linuxppc-...@lists.ozlabs.org
Reviewed
When direct read IO is submitted from kernel, it is often
unnecessary to dirty pages, for example of loop, dirtying pages
have been considered in the upper filesystem(over loop) side
already, and they don't need to be dirtied again.
So this patch doesn't dirtying pages for ITER_BVEC/ITER_KVEC
dire
This patches provides one interface for enabling direct IO
from user space:
- userspace(such as losetup) can pass 'file' which is
opened/fcntl as O_DIRECT
Also __loop_update_dio() is introduced to check if direct I/O
can be used on current loop setting.
The last big change is to
There are about 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
- in buffere
If loop block is mounted via 'mount -o loop', it isn't easy
to pass file descriptor opened as O_DIRECT, so this patch
introduces a new command to support direct IO for this case.
Cc: linux-...@vger.kernel.org
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 19 +++
include
From: Kan Liang
When multiple events are sampled it may not be needed to collect
callgraphs for all of them. The sample sites are usually nearby, and
it's enough to collect the callgraphs on a reference event (such as
precise cycles or precise instructions).
This patchkit adds the ability to turn
From: Kan Liang
This patchkit adds the ability to turn off time stamps per event.
One usable case of partial time is to work with per-event callgraph to
enable "PEBS threshold > 1" (https://lkml.org/lkml/2015/5/10/196), which
can significantly reduce the sampling overhead.
The event samples with
From: Kan Liang
This patchkit adds the ability to turn off callgraphs and time stamps
per event. This in term can reduce sampling overhead and the size of
the perf.data.
Changes since V1:
- Break up V1 patches into three patches(parse option changes,
partial time support and partial callgr
From: Kan Liang
Add tests in tests/parse-events.c to check callgrap and time option
Signed-off-by: Kan Liang
---
tools/perf/tests/parse-events.c | 28
1 file changed, 28 insertions(+)
diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
i
From: Kan Liang
Introduce callgraph_set to indicate whether the callgraph option was set
by user.
Signed-off-by: Kan Liang
---
tools/perf/builtin-record.c | 6 --
tools/perf/perf.h | 1 +
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/perf/builtin-record.c b
On Thu, Jul 16, 2015 at 04:04 AM CEST, Sreenath Madasu
wrote:
> This one of the TODO tasks for staging rtl8188eu driver. I have removed
> the code referring to channel > 14 for rtw_ap.c, rtw_ieee80211.c and
> rtw_mlme.c files. Please review.
>
> Signed-off-by: Sreenath Madasu
I would consider r
On Wed, 8 Jul 2015, Andy Shevchenko wrote:
> Intel Tangier has an IOSF Mailbox with PCI ID 8086:1170.
>
> While here, keep list ordered by ID.
I skipped that ordering part, because the result is horrible to
read. Alphabetic ordering in both places is the right thing.
Thanks,
tglx
--
To
On Thu, Jul 16, 2015 at 4:46 AM, Brian Gerst wrote:
> Move the userspace accesses down into the common function in
> preparation for the next set of patches.
Nice!
Could you improve the changelog a bit? You're really changing the way
it works (in a good way).
> - set_flags(regs->pt.flags
On Thu, Jul 16, 2015 at 08:35:58AM -0700, Joe Perches wrote:
> > #31:
> > arch/x86/kernel/hpet.c | 198
> > ++---
I guess those are in the limbo land between the end of message and
beginning of the patch itself. Perhaps the test should at least stop a
On Thu, Jul 16, 2015 at 5:40 AM, Denys Vlasenko wrote:
> This patch deinlines jhash, jhash2 and __jhash_nwords.
>
> It also removes rhashtable_jhash2(key, length, seed)
> because it was merely calling jhash2(key, length, seed).
>
> With this .config: http://busybox.net/~vda/kernel_config,
> after
On Thu, 2015-07-16 at 17:20 +0200, Joerg Roedel wrote:
> On Tue, Jul 14, 2015 at 02:48:53PM -0600, Alex Williamson wrote:
> > This continues the attempt to fix commit fb170fb4c548 ("iommu/vt-d:
> > Introduce helper functions to make code symmetric for readability").
> > The previous attempt in comm
On Thu, 9 Jul 2015, Julien Grall wrote:
> Only use the first 4KB of the page to store the events channel info. It
> means that we will wast 60KB every time we allocate page for:
^ waste
> * control block: a page is allocating per CPU
> * event array: a page is alloc
On Thu, Jul 16, 2015 at 4:46 AM, Brian Gerst wrote:
> There is no need to save FS and non-lazy GS outside the 32-bit regs. Lazy GS
> still needs to be saved because it wasn't saved on syscall entry.
I think I'm missing something. Why can't you just lazy_save_gs into regs32->gs?
--Andy
--
To un
On Thu, Jul 16, 2015 at 01:52:54PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2015 at 03:45:51PM +0100, Nariman Poushin wrote:
>
> Please submit patches in the format covered in SubmittingPatches,
> version information goes inside the [].
>
> > Add support for writing sequences of registers / pat
Fix a memory leak with scsi-mq triggered by commands with large data
transfer length.
__sg_alloc_table() sets both table->nents and table->orig_nents to the
same value. When the scatterlist is DMA-mapped, table->nents is
overwritten with the (possibly smaller) size of the DMA-mapped
scatterlist,
On Thu, 9 Jul 2015, Julien Grall wrote:
> The Xen interface is using 4KB page granularity. This means that each
> grant is 4KB.
>
> The current implementation allocates a Linux page per grant. On Linux
> using 64KB page granularity, only the first 4KB of the page will be
> used.
>
> We could decr
When regmap locking is done using spinlocks (e.g. using
devm_regmap_init_mmio_clk) access is protected using spin_lock_irqsave.
So when calling regmap_write the first time and a node is about to be
inserted kzalloc must not be called with GFP_KERNEL. At this point
interrupts are disabled. This fixe
On Thu, Jul 16, 2015 at 11:11:33PM +, Craig Inches wrote:
> Fixed up some checkpatch.pl style issues.
> Line greater than 80 Chars in multiple locations.
>
> Signed-off-by: Craig Inches
> ---
> drivers/staging/dgnc/dgnc_tty.c | 168
> ++--
> 1 file change
To analyze the exit events with perf, we need kvm_perf.h to be added in
the arch/powerpc directory, where the kvm tracepoints needed to trace
the KVM exit events are defined.
This patch adds "kvm_perf_book3s.h" to indicate that the tracepoints are
book3s specific. Generic "kvm_perf.h" then can jus
To analyze the hcalls with perf, we need the hcall related tracepoints
information to be exported.
This patch adds hcall tracepoints "kvm_hv:kvm_hcall_enter" and
"kvm_hv:kvm_hcall_exit" to kvm_perf.h. So, perf will now know as to what
tracepoints to look for if we are using "perf kvm stat record"
On Jul 17, 2015, at 12:31 AM, Steven Rostedt wrote:
> On Fri, 17 Jul 2015 00:01:25 +0900
> Jungseok Lee wrote:
>
>> I've gathered stack tracer data with your update.
>>
>> 1) stack_trace
>>DepthSize Location(35 entries)
>>-
>> 0) 4424 16
Commit-ID: 23ae2a16bb39d999892a86a65933fe3e9b6b525f
Gitweb: http://git.kernel.org/tip/23ae2a16bb39d999892a86a65933fe3e9b6b525f
Author: Andy Shevchenko
AuthorDate: Wed, 8 Jul 2015 17:45:05 +0300
Committer: Thomas Gleixner
CommitDate: Thu, 16 Jul 2015 17:48:47 +0200
x86/platform/iosf_mbi
Commit-ID: 64279c7e05264f9774c6c9ee65a5b9ed186e442b
Gitweb: http://git.kernel.org/tip/64279c7e05264f9774c6c9ee65a5b9ed186e442b
Author: Andy Shevchenko
AuthorDate: Wed, 8 Jul 2015 17:45:06 +0300
Committer: Thomas Gleixner
CommitDate: Thu, 16 Jul 2015 17:48:48 +0200
x86/platform/iosf_mbi
Commit-ID: 7e1ff15b699bcb2bce1e8086323d227788960044
Gitweb: http://git.kernel.org/tip/7e1ff15b699bcb2bce1e8086323d227788960044
Author: Andy Shevchenko
AuthorDate: Wed, 8 Jul 2015 17:45:08 +0300
Committer: Thomas Gleixner
CommitDate: Thu, 16 Jul 2015 17:48:48 +0200
x86/platform/iosf_mbi
Commit-ID: f33d159ea701cbaba90f20876aeba11d27b698c2
Gitweb: http://git.kernel.org/tip/f33d159ea701cbaba90f20876aeba11d27b698c2
Author: Andy Shevchenko
AuthorDate: Wed, 8 Jul 2015 17:45:09 +0300
Committer: Thomas Gleixner
CommitDate: Thu, 16 Jul 2015 17:48:48 +0200
x86/platform/iosf_mbi
On 07/16/2015 04:05 AM, Kirill A. Shutemov wrote:
>> > These both look nice to me (and they both cull specialty MPX code which
>> > is excellent). I'll run them through a quick test.
> Any update?
Both patches look fine to me and test OK. Feel free to add my
acked/tested/etc...
--
To unsubscribe
Hi Waiman,
On Thu, Jul 09, 2015 at 05:32:21PM +0100, Waiman Long wrote:
> v1->v2:
> - Take out patch 1 which had been merged to tip.
> - Take out patch 4 as the change may impact light load performance
> - Rebased to the latest tip branch
>
> In converting some existing spinlocks to rwlock, it
Commit-ID: b93fb9f6aee0ea6fe60ed20278b9c7fea70a58ff
Gitweb: http://git.kernel.org/tip/b93fb9f6aee0ea6fe60ed20278b9c7fea70a58ff
Author: Andy Shevchenko
AuthorDate: Wed, 8 Jul 2015 17:45:07 +0300
Committer: Thomas Gleixner
CommitDate: Thu, 16 Jul 2015 17:48:48 +0200
x86/platform/iosf_mbi
401 - 500 of 994 matches
Mail list logo
