Hi Joerg,
On 7/2/2015 2:52 PM, Joerg Roedel wrote:
Hi Jin,
On Thu, Jul 02, 2015 at 12:24:34PM +0800, xiao jin wrote:
[ 106.107851] BUG: unable to handle kernel NULL pointer dereference at
0040
[ 106.116702] IP:
[ 106.118490] []
check_irq_vectors_for_cpu_disable+0x76/0x180
Th
On 2015年07月01日 19:52, Heiko Stübner wrote:
Hi Mark,
Am Mittwoch, 1. Juli 2015, 17:49:33 schrieb Mark Yao:
hardware cursor windows only have some fixed size, and not support
width virtual, when move hardware cursor windows outside of left,
the display would be wrong, so this window can't for cur
On Thursday 02 July 2015 04:02 AM, Joel Porquet wrote:
> At the moment the IRQCHIP_DECLARE macro is only declared locally in
> 'drivers/irqchip/irqchip.h'. That prevents from using it directly in arch/*
> directories whenever irqchip drivers only exist there, which happens in a few
> cases (e.g. ar
Hi Mark
Can I have some feedback about these patches ?
> Current _regmap_update_bits() writes data to register if current value and
> write value was different. This means it doesn't write data if the value was
> same as current value.
> But, some device needs to write data even though it was sa
On Thu, Jul 2, 2015 at 3:53 PM, Mark yao wrote:
> Hi Tomasz
> Thanks for your review, I will fix it soon.
>
> On 2015年07月02日 14:00, Tomasz Figa wrote:
>>
>> Hi Mark,
>>
>> Please see my comments inline.
>>
>> On Fri, Jun 26, 2015 at 7:07 PM, Mark Yao wrote:
>>>
>>> vop support yuv with NV12,
hardware cursor windows only have some fixed size, and not support
width virtual, when move hardware cursor windows outside of left,
the display would be wrong, so this window can't for cursor now.
And Tag hardware cursor window as a overlay is wrong, will make
userspace wrong behaviour.
So just
Thanks for the support. I will create v3 based with LED triggers.
Just for information. ASUS's wording is as below:
Fn+F2 can be used to turn on or off all radio capabilities in the
device (as known as airplane mode switch). I don't have any
preferences on the name. We may use the term airpla
On Thursday 07 May 2015 11:32 AM, Vineet Gupta wrote:
> Hi Greg,
>
> Upstream commit e4140819dadc3624accac8294881bca8a3cba4ed, "ARC: signal
> handling
> robustify" was marked for stable inclusion. It made it into 3.18 but not
> earlier
> likely due to interim changes preventing a clean merge.
>
Hello,
We have two basic load balancing: idle blancing and periodic balancing.
It takes a tick for periodic balancing to happen again, so the livelock
could not be from it.
On the contrary, the idle balancing occurs as needed at arbitrary time,
so the livelock could happen.
And obviously, the i
Dne 2.7.2015 v 08:47 Geert Uytterhoeven napsal(a):
> On Thu, Jul 2, 2015 at 2:30 AM, Stephen Rothwell
> wrote:
>> Today's linux-next merge of the kbuild tree got a conflict in:
>>
>> scripts/kconfig/Makefile
>>
>> between commits:
>>
>> 9bcd776d299e ("kconfig: clarify kvmconfig is for kvm")
>
Hi,
Greg Kroah-Hartman wrote:
> On Fri, Jun 26, 2015 at 09:20:19PM -0400, Alan Stern wrote:
> > I can test it next week, if you would like to see the actual values.
> That would be great.
That one? (plus mouse plugged into keyboard hub)
http://lisas.de/~andi/lkml/Apple_A1048_lsusb/
HTH,
Andre
pdata is used before NULL check, so it looks misleading.
If pdata validation is required then we have to
first check for pdata validation, then calculate id,
and then second check for pdata->dcdc[id].
and it is better to use !pointer then to use (pointer == NULL)
Signed-off-by: Maninder Singh
--
On Thursday 02 July 2015 12:40 PM, Vineet Gupta wrote:
> On Thursday 07 May 2015 11:32 AM, Vineet Gupta wrote:
>> Hi Greg,
>>
>> Upstream commit e4140819dadc3624accac8294881bca8a3cba4ed, "ARC: signal
>> handling
>> robustify" was marked for stable inclusion. It made it into 3.18 but not
>> earlie
The virtio_ring.h header is used in userspace programs (ie. QEMU),
too. Here we can not assume that sizeof(pointer) is the same as
sizeof(long), e.g. when compiling for Windows, so the typecast in
vring_init() should be done with (uintptr_t) instead of (unsigned long).
Signed-off-by: Thomas Huth
On Wed 01-07-15 13:45:15, Nicholas Krause wrote:
> This makes the function set_recommended_min_free_kbytes have a
> return type of void now due to this particular function never
> needing to signal it's call if it fails due to this function
> always completing successfully without issue.
The chang
> On Wed, Jun 24, 2015 at 10:31:09PM -0300, Julio Faracco wrote:
> > 2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin :
> > >
> > > On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> > > > virtio_net paravirtualized driver does not have a tx_timeout() function
> > > > to
> > > > guarante
On Wed 01-07-15 14:27:57, Nicholas Krause wrote:
> This makes the function zap_huge_pmd have a return type of bool
> now due to this particular function always returning one or zero
> as its return value.
How does this help anything? IMO this just generates a pointless churn
in the code without a
Hello!
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf
> Of Eric Auger
> Sent: Monday, June 29, 2015 6:37 PM
> To: eric.au...@st.com; eric.au...@linaro.org;
> linux-arm-ker...@lists.infradead.org;
> marc.zyng...@arm.com; christoffer.d.
On Wed, Jul 01, 2015 at 12:24:37PM +0300, Jarkko Sakkinen wrote:
> The compat ioctl handler ends up calling access_ok() twice: first
> indirectly inside compat_alloc_user_space() and then after returning
> from that function. This patch fixes issue.
>
> Signed-off-by: Jarkko Sakkinen
Applied to
On 02.07.2015 15:40, Chanwoo Choi wrote:
> This patch removes the unused code related to struct exynos_tmu_platform_data
> because exynos_tmu_probe() don't handle the struct exynos_tmu_platform_data
> *pdata.
>
> Cc: Zhang Rui
> Cc: Eduardo Valentin
> Cc: Lukasz Majewski
> Signed-off-by: Chanw
Hello Krzysztof,
The information provided to userspace is not accurate in current driver
implementation and it is accurate with this patch.
Also, when the battery is reconnected to the charger (after it has been
disconnected from the charger), the charger does not trigger any
interrupt. Since
These changes allow a PHY driver to trigger a VBUS interrupt and
to provide the value of VBUS.
Signed-off-by: Phil Edworthy
---
v2:
- vbus variables changed from int to bool.
- dev_info() changed to dev_err()
---
drivers/usb/renesas_usbhs/common.h | 2 ++
drivers/usb/renesas_usbhs/mod.
On 06/16/2015 10:51 AM, Kuninori Morimoto wrote:
Hi Mark
Current _regmap_update_bits() writes data to register if current value and
write value was different. This means it doesn't write data if the value was
same as current value.
But, some device needs to write data even though it was same va
* Paul E. McKenney wrote:
> On Wed, Jul 01, 2015 at 07:02:42PM +0200, Peter Zijlstra wrote:
> > On Wed, Jul 01, 2015 at 09:17:05AM -0700, Paul E. McKenney wrote:
> > > On Wed, Jul 01, 2015 at 04:17:10PM +0200, Peter Zijlstra wrote:
> >
> > > > 74b51ee152b6 ("ACPI / osl: speedup grace period in
> > +
> > +- pad-select: should specify spi pad used, only required for MT8173.
> > + This value should be 0~3.
> > +
> > +Example:
> > +
> > +- SoC Specific Portion:
> > +spi: spi@1100a000 {
> > + compatible = "mediatek,mt8173-spi";
> > + reg = <0 0x1100a000 0 0x1000>;
> > +
On Thu, Jul 02, 2015 at 10:19:07AM +0300, Andrey Ryabinin wrote:
> On 07/02/2015 07:10 AM, Al Viro wrote:
> >>
> >> It should be easy to confirm - in p9_client_prepare_req() add
> >>if (WARN_ON_ONCE(tag != (u16)tag)) {
> >>p9_idpool_put(tag, c->tagpool);
> >>
[repeating, since my previous email didn't reach mailing lists]
2015-07-02 7:10 GMT+03:00 Al Viro :
>> It should be easy to confirm - in p9_client_prepare_req() add
>> if (WARN_ON_ONCE(tag != (u16)tag)) {
>> p9_idpool_put(tag, c->tagpool);
>>
Hello!
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf
> Of Eric Auger
> Sent: Monday, June 29, 2015 6:37 PM
> To: eric.au...@st.com; eric.au...@linaro.org;
> linux-arm-ker...@lists.infradead.org;
> marc.zyng...@arm.com; christoffer.d.
On Thu, Jul 02, 2015 at 10:48:31AM +0530, Lokesh Vutla wrote:
> OMAP AES driver returns an error if the data is not aligned with
> AES_BLOCK_SIZE bytes.
> But OMAP AES hw allows data input upto 1 byte aligned, but still
> zeros are to be appended and complete AES_BLOCK_SIZE has to be written.
> And
Le 01/07/2015 22:35, Kevin Hilman a écrit :
> Nicolas Ferre writes:
>
>> From: Boris Brezillon
>>
>> at91sam9g45, at91sam9x5 and sama5 SoCs should not use
>> "atmel,at91sam9rl-udc" for their USB device compatible property since
>> this compatible is attached to a specific hardware bug fix.
>>
>>
On Thu, 2015-07-02 at 08:39 +0200, Joerg Roedel wrote:
> On Thu, Jul 02, 2015 at 01:14:18PM +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > commit 571dbbd4d044e11c78bc077acb3ccef4c77b096e ("i
* Andrey Ryabinin wrote:
> On 07/01/2015 12:07 PM, Ingo Molnar wrote:
> >
> > * Andrey Ryabinin wrote:
> >
> >> diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
> >> index 5a46681..f129a9a 100644
> >> --- a/arch/x86/kernel/head64.c
> >> +++ b/arch/x86/kernel/head64.c
> >> @@ -
On Thu, Jul 02, 2015 at 10:48:32AM +0530, Lokesh Vutla wrote:
> AES_CTRL_REG is used to configure AES mode. Before configuring
> any mode we need to make sure all other modes are reset or else
> driver will misbehave. So mask all modes before configuring
> any AES mode.
>
> Signed-off-by: Lokesh V
pdata is used before NULL check, so it looks misleading.
If pdata validation is required then we have to
first check for pdata validation, then calculate id,
and then second check for pdata->dcdc[id].
and it is better to use !pointer than (pointer == NULL)
Signed-off-by: Maninder Singh
---
v2: i
On Thu, Jul 02, 2015 at 10:48:33AM +0530, Lokesh Vutla wrote:
> Add aead_request_cast() api to get pointer to aead_request
> from cryto_async_request.
>
> Signed-off-by: Lokesh Vutla
> ---
> include/linux/crypto.h |6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/c
On Thu, Jul 02, 2015 at 10:48:34AM +0530, Lokesh Vutla wrote:
> Use BIT()/GENMASK() macros for all register definitions instead of
> hand-writing bit masks.
>
> Signed-off-by: Lokesh Vutla
> ---
> drivers/crypto/omap-aes.c | 36 ++--
> 1 file changed, 18 inserti
On Thu, Jul 02, 2015 at 10:50:05AM +0300, Andrey Ryabinin wrote:
> >> and see if it triggers. I'm not sure if failing with ENOMEM is the
> >> right response (another variant is to sleep there until the pile
> >> gets cleaned or until we get killed), and WARN_ON_ONCE() is definitely
> >> not for t
Am Donnerstag, 2. Juli 2015, 10:48:38 schrieb Lokesh Vutla:
Hi Lokesh,
>Now the driver supports gcm mode, add omap-aes-gcm
>algo info to omap-aes driver.
>
>Signed-off-by: Lokesh Vutla
>---
> drivers/crypto/omap-aes.c | 22 ++
> 1 file changed, 22 insertions(+)
>
>diff --git
On Thu, Jul 02, 2015 at 10:48:35AM +0530, Lokesh Vutla wrote:
> OMAP AES hw supports aes gcm mode.
here you refer to it as 'gcm'
> Adding support for GCM mode in omap-aes driver.
while here and in subject as 'GCM'.
> Signed-off-by: Lokesh Vutla
> ---
> drivers/crypto/Makefile |3 +-
On Thu, Jul 02, 2015 at 10:48:37AM +0530, Lokesh Vutla wrote:
> Check if the inputs are not aligned, if not process
> the input before starting the hw acceleration.
> Similarly after completition of hw acceleration.
>
> Signed-off-by: Lokesh Vutla
and this ?
--
balbi
signature.asc
Descriptio
On Thu, Jul 02, 2015 at 10:48:36AM +0530, Lokesh Vutla wrote:
> Its not necessary that assoc data and plain text is passed always.
> Add these checks before processing the input.
>
> Signed-off-by: Lokesh Vutla
why can't this be combined with patch which added GCM in the first
place ?
> ---
>
On Thu, 2015-07-02 at 07:25 +0800, Yuyang Du wrote:
> That being said, it is also obvious to prevent the livelock from happening:
> idle pulling until the source rq's nr_running is 1, becuase otherwise we
> just avoid idleness by making another idleness.
Yeah, but that's just the symptom, not the
On Thu, Jul 02, 2015 at 10:48:39AM +0530, Lokesh Vutla wrote:
> Add support for PIO mode for GCM mode.
>
> Signed-off-by: Lokesh Vutla
why do you require PIO ? Is there any situation where DMA can't be
used? What would that case be ?
--
balbi
signature.asc
Description: Digital signature
On Wed, 01 Jul 2015, Jarkko Sakkinen wrote:
> The compat ioctl handler ends up calling access_ok() twice: first
> indirectly inside compat_alloc_user_space() and then after returning
> from that function. This patch fixes issue.
>
> Signed-off-by: Jarkko Sakkinen
> ---
> drivers/gpu/drm/drm_ioc3
Instead of statically selecting the PHY connection to either the
USBHS (Function) or PCI0 (Host) IP blocks, this change allows the
dts to specifiy gpio pins for the vbus and id signals. Additional
gpio pins are used to control power to an external OTG device and
an override to turn vbus on/off.
No
Hi,
commit ed013214afa7 ("ACPI / init: Make it possible to override _REV")
is in today's linux-next tree (i.e., next-20150702) adding the
following hunk to drivers/acpi/Kconfig:
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -428,6 +428,26 @@ config XPOWER_PMIC_OPREGI
On Mon, Jun 29, 2015 at 11:03 PM, YH Huang wrote:
> Add display PWM driver support to modify backlight for MT8173 and MT6595.
> The PWM has one channel to control the brightness of the display.
> When the (high_width / period) is closer to 1, the screen is brighter;
> otherwise, it is darker.
>
>
Hi Phil,
(CC'ing Morimoto-san)
Thank you for the patch.
On Thursday 02 July 2015 08:36:42 Phil Edworthy wrote:
> These changes allow a PHY driver to trigger a VBUS interrupt and
> to provide the value of VBUS.
>
> Signed-off-by: Phil Edworthy
>
> ---
> v2:
> - vbus variables changed from in
On Mon, Jun 29, 2015 at 11:24 PM, YH Huang wrote:
> I am sorry for forgetting to remove Change-Id in [PATCH v3 1/2] and
> [PATCH v3 1/2].
>
> Regards,
> YH Huang
>
> On Mon, 2015-06-29 at 23:03 +0800, YH Huang wrote:
>> Document the device-tree binding of MediatTek display PWM.
>> The clock "main"
Both USB Host (pci0) and Function (USBHS) drivers are enabled.
The USB PHY driver determines which IP block should be connected
based on vbus and id signals read via gpios.
Note that switch SW5 and SW6 on Koelsch board needs to be set to
position 3 for this to work.
---
Not for upstream until th
On 07/02/2015 10:59 AM, Al Viro wrote:
> On Thu, Jul 02, 2015 at 10:50:05AM +0300, Andrey Ryabinin wrote:
>
and see if it triggers. I'm not sure if failing with ENOMEM is the
right response (another variant is to sleep there until the pile
gets cleaned or until we get killed), and W
Hi Alexey,
> > +config SPI_MT65XX
> > + tristate "MediaTek SPI controller"
> > + depends on ARCH_MEDIATEK || COMPILE_TEST
> > + help
> > + This selects the MediaTek(R) SPI bus driver.
> > + If you want to use MediaTek(R) SPI interface,
> > + say Y or M her
Hi,
On Monday 22 June 2015 08:12 PM, Phil Edworthy wrote:
> Instead of statically selecting the PHY connection to either the
> USBHS (Function) or PCI0 (Host) IP blocks, this change allows the
> dts to specifiy gpio pins for the vbus and id signals. Additional
> gpio pins are used to control power
Le 02/07/2015 00:53, Matteo Croce a écrit :
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Dest-Unreach for UDP.
Also disables ICMP replies to echo request and timestamp.
The stealth mode can be enabled selectively for a single interface.
---
in
On Thu, Jul 02, 2015 at 11:19:03AM +0300, Andrey Ryabinin wrote:
> Besides qemu, I've also tried kvmtool with the same result. IOW I'm seeing
> this under kvmtool as well. It just takes a bit longer to reproduce
> this in kvmtool.
>
> > The bug I suspected to be the cause of that is in tag allocat
The variable "desc" is only used for storing the return value at the
end of the function. It is is unneeded.
Signed-off-by: Masahiro Yamada
---
drivers/gpio/gpiolib-of.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.
Hello Dear Friend,
This is Kabiru I have a deal worth $15.5 million dollar from my bank
that requires me to involve a foreigner, please if you will be
interested to help me out, I advise you to reply back to my
confidential mail ID (k.wahid...@terra.com) for more detail about the
transaction and wh
Hello,
I'm sorry to bother you with this, but lwn.net reported a rather serious
security issue a couple of weeks ago:
http://lwn.net/Articles/646590/
https://bugzilla.redhat.com/show_bug.cgi?id=1202855
CVE-2015-1805
"It was found that the Linux kernel's implementation of vectored pipe
read and wr
Hi Greg
A set of 6 patches to drop unused code and fix some bugs:
#1: simple fix for test-cases
#2: drop redundant internal accounting
#3: drop unused structure member
#4: drop support for an HELLO-ioctl item that was never used. If this breaks
some user-space we're not aware of, we will
This drops the KDBUS_ITEM_ATTACH_FLAGS_RECV item from KDBUS_CMD_BUS_MAKE.
This item was used to provide an attach-flags mask which defines metadata
items that all connections must have in their send-mask. Hence,
effectively forcing the transmission of such items in case the receiver
wants them.
Th
We now support CAP translations. Make sure our tests reflect that. So far
they made sure we drop CAPS on namespace borders. This is wrong, though.
We really need to just make sure that no _or_ the correctly translated
caps are returned. Fix this.
Signed-off-by: David Herrmann
---
tools/testing/s
This field is never used, drop it.
Signed-off-by: David Herrmann
---
ipc/kdbus/message.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/ipc/kdbus/message.h b/ipc/kdbus/message.h
index cdaa65c..3b73347 100644
--- a/ipc/kdbus/message.h
+++ b/ipc/kdbus/message.h
@@ -88,7 +88,6 @@ kdbus_msg_re
Right now, we always assume an activator has a valid name and
conn->activator_of is set. However, this assumption is not true if the
setup of the activator fails. In those cases, the ->flags field indicates
an activator, but the name might not have been claimed, yet.
Fix the destructor of connecti
Whenever we send messages to a target connection, all we know about the
target is the 'struct file' associated with the kdbus connection. Hence,
we cannot know which namespaces a receiving process will be in when it
calls KDBUS_CMD_RECV on the message. So far, we pinned all metadata we
wanna send a
We already limit the size of the message object, there's no reason to add
an arbitrary additional limit on the number of items. We don't do this for
other item-arrays, so lets stop restricting the messages in this way.
Signed-off-by: David Herrmann
---
ipc/kdbus/limits.h | 3 ---
ipc/kdbus/mess
Hi
On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> Signed-off-by: Sergei Zviagintsev
> ---
> ipc/kdbus/connection.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
(I'm a fan of putting the actual typo-corrections into the
commit-msg-body, like: "allocations -> allocat
Hi
On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> uint{8,16,32}_t -> u{8,16,32}
>
> Signed-off-by: Sergei Zviagintsev
> ---
> ipc/kdbus/connection.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: David Herrmann
Thanks
David
> diff --git a/ipc/kdbus/
Hi
On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> Replace the use of max() with explicit and obvious overflow check.
>
> Signed-off-by: Sergei Zviagintsev
> ---
> ipc/kdbus/connection.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/ipc/kdbus/connec
Hi Laurent,
On 02 July 2015 09:15, Laurent wrote:
> Hi Phil,
>
> (CC'ing Morimoto-san)
>
> Thank you for the patch.
>
> On Thursday 02 July 2015 08:36:42 Phil Edworthy wrote:
> > These changes allow a PHY driver to trigger a VBUS interrupt and
> > to provide the value of VBUS.
> >
> > Signed-of
When wlcore_probe_of failed, return the correct error code instead of ENOMEM
Signed-off-by: Raphaël Poggi
---
drivers/net/wireless/ti/wlcore/sdio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ti/wlcore/sdio.c
b/drivers/net/wireless/ti/wlcore/sdio.c
Hi
On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> If we spotted inconsistency, fix it by setting values to zero.
Why?
I prefer doing nothing and just bailing out on programming errors.
Setting it to 0 just complicates debugging and drops possibly useful
information ('what was the
Am 01.07.2015 um 16:14 schrieb Ohad Ben-Cohen:
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git
tags/remoteproc-
rtc_sysfs_add_device checks if device can wakeup before creating the
wakealarm file in sysfs. Thus the driver must set wakeup capability
before registering the rtc device.
Signed-off-by: Wei-Ning Huang
---
drivers/rtc/rtc-mt6397.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
Also disables ICMP replies to echo request and timestamp.
The stealth mode can be enabled selectively for a single interface.
Signed-off-by: Matteo Croce
---
Documentation/n
Hello!
> What if we use KVM_MSI_VALID_DEVID flag instead of new
> KVM_IRQ_ROUTING_EXTENDED_MSI
> definition? I
> believe this would make an API more consistent and introduce less new
> definitions.
I have just found one more flaw in your implementation. If you take a look at
irqfd_wakeup()..
On Thu, Jul 02, 2015 at 09:25:30AM +0100, Al Viro wrote:
> On Thu, Jul 02, 2015 at 11:19:03AM +0300, Andrey Ryabinin wrote:
> > Besides qemu, I've also tried kvmtool with the same result. IOW I'm seeing
> > this under kvmtool as well. It just takes a bit longer to reproduce
> > this in kvmtool.
> >
On Wed, 2015-07-01 at 10:06 +0100, Daniel P. Berrange wrote:
> I don't really think it is sensible to be defining & implementing new
> network services which can't support strong encryption and authentication.
> Rather than passing the file descriptor to the kernel and having it do
> the I/O direc
This RFC series is another evolution of the attempt to deal with THP
allocations latencies. Please see the motivation in the previous version [1]
The main difference here is that I've bitten the bullet and implemented
per-node kcompactd kthreads - see Patch 1 for the details of why and how.
Trying
Khugepaged tries to preallocate a hugepage before scanning for THP collapse
candidates. If the preallocation fails, scanning is not attempted. This makes
sense, but it is only restricted to !NUMA configurations, where it does not
need to predict on which node to preallocate.
Besides the !NUMA rest
Memory compaction can be currently performed in several contexts:
- kswapd balancing a zone after a high-order allocation failure
- direct compaction to satisfy a high-order allocation, including THP page
fault attemps
- khugepaged trying to collapse a hugepage
- manually from /proc
The purpose
Since we track hugepage availability for khugepaged THP collapses, we can use
it also for page fault THP allocations. If hugepages are considered unavailable
on a node, the cost of reclaim/compaction during the page fault could be easily
higher than any THP benefits (if it at all succeeds), so we b
Hi Alex,
On Wed, Jul 01, 2015 at 07:29:01PM +0100, Alex Bennée wrote:
> This adds support for userspace to control the HW debug registers for
> guest debug. In the debug ioctl we copy an IMPDEF registers into a new
> register set called host_debug_state.
>
> We use the recently introduced vcpu pa
Khugepaged could be scanning for collapse candidates uselessly, if it cannot
allocate a hugepage for the actual collapse event. The hugepage preallocation
mechanism has prevented this, but only for !NUMA configurations. It was
removed by the previous patch, and this patch replaces it with a more g
On Thu, 2015-07-02 at 16:36 +0800, Wei-Ning Huang wrote:
> rtc_sysfs_add_device checks if device can wakeup before creating the
> wakealarm file in sysfs. Thus the driver must set wakeup capability
> before registering the rtc device.
>
> Signed-off-by: Wei-Ning Huang
> ---
> drivers/rtc/rtc-mt6
Le 02/07/2015 10:38, Matteo Croce a écrit :
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
Also disables ICMP replies to echo request and timestamp.
The stealth mode can be enabled selectively for a single interface.
Sig
Hi Tomeu,
On Wed, Jul 1, 2015 at 2:45 PM, Tomeu Vizoso wrote:
> When an OF node has a pin range for its GPIOs, return -EPROBE_DEFER if
> the pin controller isn't available.
>
> Otherwise, the GPIO range wouldn't be set at all unless the pin
> controller probed always before the GPIO chip.
>
> Wit
Hi!
I'm not subscribed, so plese CC: me for your replies.
When graphing the CPU load, I noticed that the 15-minute average never drops
below 0.05, while the 5-minute load and the 1-minute load does
(Kernel 3.0.101-0.47.52-xen of SLES11 on x86_64).
Ist that a known bug? Interactive call of "upti
On Wed, Jul 01, 2015 at 03:18:04PM -0700, Paul E. McKenney wrote:
> On Wed, Jul 01, 2015 at 12:27:17PM +0200, Peter Zijlstra wrote:
> > That wants to be an ACQUIRE, right?
>
> I cannot put the acquire in the WARN_ON_ONCE() because there
> are configurations where WARN_ON_ONCE() is compiled out.
On Wed, Jul 01, 2015 at 11:07:08AM +0200, Igor Mammedov wrote:
> changes since v2:
> * drop cache patches for now as suggested
> * add max_mem_regions module parameter instead of unconditionally
> increasing limit
> * drop bsearch patch since it's already queued
I get non-trivial conflic
Hi
On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> 1) Rewrite
>
> quota->memory + memory > U32_MAX
>
> as
> U32_MAX - quota->memory < memory
>
> and provide the comment on why we need that check.
>
> We have no overflow issue in the original expression wh
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 93472aff802fd7b61f2209335207e9bd793012f7:
>
> perf/x86: Fix 'active_events' imbalance (2015-06-30 13:08:46 +0200)
>
> are available in the git repository at
Hm, had to unpull it, due to:
make[3]: *** No rule to make target 'util/intel-pt.h', needed by
'util/auxtrace.o'. Stop.
/home/mingo/tip/tools/build/Makefile.build:107: recipe for target 'util' failed
make[2]: *** [util] Error 2
Makefile.perf:373: recipe for target 'libperf-in.o' failed
make[1]:
Hi Mike,
On Thu, Jul 02, 2015 at 10:05:47AM +0200, Mike Galbraith wrote:
> On Thu, 2015-07-02 at 07:25 +0800, Yuyang Du wrote:
>
> > That being said, it is also obvious to prevent the livelock from happening:
> > idle pulling until the source rq's nr_running is 1, becuase otherwise we
> > just av
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
Also disables ICMP replies to echo request and timestamp.
The stealth mode can be enabled selectively for a single interface.
Signed-off-by: Matteo Croce
---
check the patch
Hi Lars
> > Current _regmap_update_bits() writes data to register if current value and
> > write value was different. This means it doesn't write data if the value was
> > same as current value.
> > But, some device needs to write data even though it was same value.
>
> Can you go into more deta
Hi Rob,
On Wed, Jul 1, 2015 at 7:36 PM, Rob Herring wrote:
> On Wed, Jul 1, 2015 at 7:45 AM, Tomeu Vizoso
> wrote:
>> When an OF node has a pin range for its GPIOs, return -EPROBE_DEFER if
>> the pin controller isn't available.
>>
>> Otherwise, the GPIO range wouldn't be set at all unless the p
[Dropped Yann. You already know Yann disappeared.]
On Thu, 2015-07-02 at 10:08 +0200, Valentin Rothberg wrote:
> commit ed013214afa7 ("ACPI / init: Make it possible to override _REV")
> is in today's linux-next tree (i.e., next-20150702) adding the
> following hunk
Changes since v1:
Split 'fix kasan shadow region page tables' into two patches:
* x86_64: kasan: fix kasan shadow region page tables
* x86_64, init: clear init_level4_pgt earlier
Alexander Popov (1):
x86_64: kasan: fix kasan shadow region page tables
Andr
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This is the start of improving fuse scalability.
An input queue and a processing queue is split out from the monolithic fuse
connection, each of those having their own spinlock. The end of t
Currently x86_64_start_kernel() has two kasan related
function calls. The first call maps shadow to early_level4_pgt,
the second maps shadow to init_level4_pgt.
If we move clear_page(init_level4_pgt) earlier, we could hide
kasan low level detail from generic x86_64 initialization code.
The next pa
1 - 100 of 608 matches
Mail list logo
