Mukesh Rathor | 21 Aug 04:16 2014

[V0 PATCH 0/2] AMD PVH domU support


Here's first stab at AMD PVH domU support. Pretty much the only thing
needed is EFER bits set. Please review.


Hayes Wang | 21 Aug 04:12 2014

RE: [PATCH net-next 3/4] r8152: remove clear_bp function

: Sergei Shtylyov [mailto:sergei.shtylyov <at>] 
> Sent: Wednesday, August 20, 2014 8:01 PM
> To: Hayes Wang; netdev <at>
> Cc: nic_swsd; linux-kernel <at>; linux-usb <at>
> Subject: Re: [PATCH net-next 3/4] r8152: remove clear_bp function
> >   	r8152b_disable_aldps(tp);
> >
> > -	rtl_clear_bp(tp);
> >
>     Why leave 2 empty lines? One is enough.

The next patch would use another fucntion at the
same location. I skip removing the empty line and
re-adding it again. Is that better to do so? I would
resend the patches if the answer is yes.

Best Regards,
Axel Lin | 21 Aug 04:11 2014

[PATCH] regulator: core: Add back the const qualifier for ops of struct regulator_desc

Fix below build warning:
CC [M]  drivers/regulator/hi6421-regulator.o
drivers/regulator/hi6421-regulator.c:356:2: warning: initialization discards 'const' qualifier
from pointer target type [enabled by default]

This is a revert of commit 716845ebeb50 ("regulator: core: Fix build error due
to const qualifier for ops"). The build error was fixed by commit 39f5460d7f9c
("regulator: core: add const to regulator_ops and fix build error in mc13892").

Signed-off-by: Axel Lin <axel.lin <at>>
 include/linux/regulator/driver.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index 3abda75..efe058f 100644
--- a/include/linux/regulator/driver.h
+++ b/include/linux/regulator/driver.h
 <at>  <at>  -246,7 +246,7  <at>  <at>  struct regulator_desc {
 	int id;
 	bool continuous_voltage_range;
 	unsigned n_voltages;
-	struct regulator_ops *ops;
+	const struct regulator_ops *ops;
 	int irq;
 	enum regulator_type type;
 	struct module *owner;


(Continue reading)

Ying Xue | 21 Aug 03:58 2014

[PATCH] acct: eliminate compile warning

If ACCT_VERSION is not defined to 3, below warning appears:
  CC      kernel/acct.o
  kernel/acct.c: In function ‘do_acct_process’:
  kernel/acct.c:475:24: warning: unused variable ‘ns’ [-Wunused-variable]

Signed-off-by: Ying Xue <ying.xue <at>>
 kernel/acct.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/kernel/acct.c b/kernel/acct.c
index b4c667d..bb52701 100644
--- a/kernel/acct.c
+++ b/kernel/acct.c
 <at>  <at>  -472,7 +472,6  <at>  <at>  static void do_acct_process(struct bsd_acct_struct *acct)
 	acct_t ac;
 	unsigned long flim;
 	const struct cred *orig_cred;
-	struct pid_namespace *ns = acct->ns;
 	struct file *file = acct->file;

 <at>  <at>  -500,9 +499,10  <at>  <at>  static void do_acct_process(struct bsd_acct_struct *acct)
 	ac.ac_gid16 = ac.ac_gid;
 #if ACCT_VERSION == 3
-	ac.ac_pid = task_tgid_nr_ns(current, ns);
+	ac.ac_pid = task_tgid_nr_ns(current, acct->ns);
-	ac.ac_ppid = task_tgid_nr_ns(rcu_dereference(current->real_parent), ns);
(Continue reading)

Chanho Min | 21 Aug 03:53 2014

[PATCH] mmc:sdhci: handle busy-end interrupt during command

It is fully legal for a controller to start handling busy-end interrupt
before it has signaled that the command has completed. So make sure
we do things in the proper order, Or it results that command interrupt
is ignored so it can cause unexpected operations. This is founded at some
toshiba emmc with the bellow warning.

"mmc0: Got command interrupt 0x00000001 even though
no command operation was in progress."

This issue has been also reported by Youssef TRIKI:
It is not specific to Toshiba devices, and happens with eMMC devices
as well as SD card which support Auto-CMD12 rather than CMD23.

Also, similar patch is submitted by:
Gwendal Grignou <gwendal <at>>

Signed-off-by: Hankyung Yu <hankyung.yu <at>>
Signed-off-by: Chanho Min <chanho.min <at>>
Tested-by: Youssef TRIKI <youssef.triki <at>>
 drivers/mmc/host/sdhci.c  |   17 +++++++++++++++--
 include/linux/mmc/sdhci.h |    1 +
 2 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 47055f3..2383be0 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
 <at>  <at>  -1007,6 +1007,7  <at>  <at>  void sdhci_send_command(struct sdhci_host *host, struct mmc_command *cmd)
 	mod_timer(&host->timer, timeout);
(Continue reading)

Namhyung Kim | 21 Aug 03:15 2014

[PATCHSET 0/2] perf hists browser: Cleanup callchain routines (v2)


This patch fixes and cleans up TUI callchain routines.  I tried to
consolidate similar functions but not to break the current output with
this change.  Hope that it makes code more readable and maintainable.

It should not change any behavior and outputs.  I verified it with
expanding by 'E' key + dumping by 'P' key on TUI and then running
"diff -u" results before and after the patchset.

Actually I have more changes that would change (or improve) some
behavior and output.  I'll post them after this patchset is merged.

 * changes in v2)
  - drop patch 1-3 in v1 since it's already merged
  - update description  (Arnaldo)
  - remove stylish changes  (Arnaldo)
  - remove unnecessary 'has_single_node' check

You can get this from 'perf/callchain-fix-v2' branch on my tree:


Any comments are welcome, thanks

Namhyung Kim (2):
  perf hists browser: Cleanup callchain print functions
  perf hists browser: Consolidate callchain print functions in TUI

(Continue reading)

Matevz Langus | 20 Aug 23:05 2014

PCI: minimal alignment of resources


I would like to ask if somebody is aware of a correct way to change they way kernel aligns PCI resources. By
default it uses minimal alignment of 1 MB.

Due to the hardware limitation I would need to change that down to 64 kB. With this change PCI Endpoints with
many small BARs would fit into limited memory space available on the RC.
This could be useful for all smaller embedded systems.

It looks just changing aligns in pbus_size_mem (in file setup-bus.c) works but not with all PCI EP drivers.
Some will crash during init.

  Matevz Langus--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo <at>
More majordomo info at
Please read the FAQ at

Kieron Browne | 20 Aug 23:21 2014

[PATCH] staging: dgnc: Fix checkpatch include warning fix. Use #include <linux/uaccess.h> instead of

Signed-off-by: Kieron Browne <kieron.browne <at>>
 drivers/staging/dgnc/dgnc_tty.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
index 281491a..c844fac 100644
--- a/drivers/staging/dgnc/dgnc_tty.c
+++ b/drivers/staging/dgnc/dgnc_tty.c
 <at>  <at>  -47,7 +47,7  <at>  <at> 
 #include <linux/serial_reg.h>
 #include <linux/slab.h>
 #include <linux/delay.h>	/* For udelay */
-#include <asm/uaccess.h>	/* For copy_from_user/copy_to_user */
+#include <linux/uaccess.h>	/* For copy_from_user/copy_to_user */
 #include <linux/pci.h>

 #include "dgnc_driver.h"


Soren Brinkmann | 20 Aug 22:55 2014

[PATCH] PM / sleep: Fix racing timers

On platforms that do not power off during suspend, successfully entering
suspend races with timers.

The race happening in a couple of location is:

  1. disable IRQs   		(e.g. arch_suspend_disable_irqs())
  2. syscore_suspend()
      -> timekeeping_suspend()
       -> clockevents_notify(SUSPEND)
        -> tick_suspend()   	(timers are turned off here)
  3. wfi            		(wait for wake-IRQ here)

Between steps 1 and 2 the timers can still generate interrupts that are
not handled and stay pending until step 3. That pending IRQ causes an
immediate - spurious - wake.

The solution is to move the clockevents suspend/resume notification
out of the syscore_suspend step and explictly call them at the appropriate
time in the suspend/hibernation paths. I.e. timers are suspend _before_
IRQs get disabled. And accordingly in the resume path.

Signed-off-by: Soren Brinkmann <soren.brinkmann <at>>

there was a little of an dicussion on the RFC for this patch, but that
eventually ended (
In the meantime I found one small flaw that is fixed in this patch (changelog
(Continue reading)

Radim Krčmář | 20 Aug 22:53 2014

[PATCH v2 0/6] Dynamic Pause Loop Exiting window.

v1 -> v2:
 * squashed [v1 4/9] and [v1 5/9] (clamping)
 * dropped [v1 7/9] (CPP abstractions)
 * merged core of [v1 9/9] into [v1 4/9] (automatic maximum)
 * reworked kernel_param_ops: closer to pure int [v2 6/6]
 * introduced ple_window_actual_max & reworked clamping [v2 4/6]
 * added seqlock for parameter modifications [v2 6/6]

PLE does not scale in its current form.  When increasing VCPU count
above 150, one can hit soft lockups because of runqueue lock contention.
(Which says a lot about performance.)

The main reason is that kvm_ple_loop cycles through all VCPUs.
Replacing it with a scalable solution would be ideal, but it has already
been well optimized for various workloads, so this series tries to
alleviate one different major problem while minimizing a chance of
regressions: we have too many useless PLE exits.

Just increasing PLE window would help some cases, but it still spirals
out of control.  By increasing the window after every PLE exit, we can
limit the amount of useless ones, so we don't reach the state where CPUs
spend 99% of the time waiting for a lock.

HP confirmed that this series prevents soft lockups and TSC sync errors
on large guests.

Radim Krčmář (6):
  KVM: add kvm_arch_sched_in
  KVM: x86: introduce sched_in to kvm_x86_ops
(Continue reading)

lilbetten6 | 20 Aug 22:36 2014

Write back!!!

Write back!!!
I, Liliane authenticate this email, you can read about me on:
I write to you because I intend to give to you a portion of my
Net-worth which I have been banking. I want to cede it out as gift
hoping it would be of help to you and others too. Respond for
confirmation to this email address: Liliabette <at>
With love,
Liliane Bettencourt
Liliabette <at>