Add a 'no_thermal' property to the power supply class. If true then
thermal zone won't be created for this power supply in
power_supply_register().
Power supply drivers may want to set it if they support
POWER_SUPPLY_PROP_TEMP and they are forwarding this get property call to
other
On 10/11/2014 10:48 PM, Eric Dumazet wrote:
On Sat, 2014-10-11 at 15:16 +0800, Jason Wang wrote:
We free transmitted packets in ndo_start_xmit() in the past to get better
performance in the past. One side effect is that skb_orphan() needs to be
called in ndo_start_xmit() which makes
added a pointer of the vortex in the following functions :
vortex_alsafmt_aspfmt
vortex_Vort3D_InitializeSource
a3dsrc_ZeroStateA3D
so that we can have a reference of the vortex in the function.
this reference of the vortex will actually be used in a later patch
to convert the pr_* macro to
pr_* macros replaced with dev_* as they are more preffered over pr_*.
each file which had pr_* was reviewed manually and replaced with dev_*.
here we have actually used the reference of the vortex which was added
to some functions in the previous patch of this series.
The prefix of the CARD_NAME
On 10/12/2014 05:27 PM, Michael S. Tsirkin wrote:
On Sat, Oct 11, 2014 at 03:16:44PM +0800, Jason Wang wrote:
Below should be useful for some experiments Jason is doing.
I thought I'd send it out for early review/feedback.
event idx feature allows us to defer interrupts until
a specific # of
Linus,
Please pull the latest locking-arch-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-arch-for-linus
# HEAD: 2291059c852706c6f5ffb400366042b7625066cd locking,arch: Use
ACCESS_ONCE() instead of cast to volatile in atomic_read()
This is a
I am Mr Tan Wong and i have a Business Proposal for you.If Interested do
contact me at my email for further details tan.wong4...@yahoo.com.hk
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
proc_ns_follow_link() is unique among the -follow_link() instances
in several respects, some of them violating general asserts expected by
all kinds of VFS code.
First of all, it can lead to vfsmount,dentry pairs with dentry
being completely unrelated to vfsmount. Suppose we bind
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-core-for-linus
# HEAD: 8acd91e8620836a56ff62028ed28ba629f2881a0 locking/lockdep: Revert
qrwlock recusive stuff
The main updates in this cycle were:
-
Hi Richard,
The signal-cleanup tree
(git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git#signal_v4)
has not bee touched since July and when merged into Linus' tree,
produces no changes (same patches different commits :-(). So all it is
doing at the moment is producing unnecessary conflicts
On 2014/10/11 11:00, Weng Meiling wrote:
ping ...
On 2014/10/9 20:47, Weng Meiling wrote:
On 2014/10/9 20:43, Weng Meiling wrote:
Hi guys,
I see the mails you discussed the BUG at fs/sysfs/group.c:65! triggered by
duplicated sysfs link.
the detail mail:
Hello Simon,
On 13-10-14 07:14, Simon Glass wrote:
Hi Jeroen,
On 12 October 2014 10:13, Jeroen Hofstee jer...@myspectrum.nl wrote:
Hello Hans,
On 12-10-14 12:25, Hans de Goede wrote:
Hi,
This one seems to have fallen through the cracks.
Regards,
Hans
(for U-boot)
nope, you replace
When system is under heavy loading, the __nfulnl_send() may may failed
to put nlmsg into skbuf of nfulnl_instance. If not clear the skbuff on failed,
the __nfulnl_send() will still try to put next nlmsg onto this half-full skbuf
and cause the user program can never receive packet.
This patch fix
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
# HEAD: cc6cd47e7395bc05c5077009808b820633eb3f18 perf/x86: Tone down kernel
messages when the PMU check fails in a virtual environment
Kernel
Oleg Nesterov o...@redhat.com writes:
On 10/08, Prarit Bhargava wrote:
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -1842,7 +1842,9 @@ static void free_module(struct module *mod)
/* We leave it in list to prevent duplicate loads, but make sure
* that noone uses it while it's
Alexey Lapitsky lex.pub...@gmail.com writes:
Hi,
I'm hitting this bug with both ext4 and btrfs.
Here's an example of the backtrace:
https://gist.github.com/vzctl/e888a821333979120932
I tried raising this BUG only for direct ring and it solved the problem:
- BUG_ON(total_sg
Michael S. Tsirkin m...@redhat.com writes:
virtio spec 0.9.X requires DRIVER_OK to be set before
VQs are used, but some drivers use VQs before probe
function returns.
Since DRIVER_OK is set after probe, this violates the spec.
Even though under virtio 1.0 transitional devices support this
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 9c2b9d30e28559a78c9e431cdd7f2c6bf5a9ee67 perf: Fix perf bug in fork()
Two leftover fixes from the v3.17 cycle - these will be
Gene Heskett wrote:
To whomever is in charge of the supposedly volatile LCK.. files in
/var/lock:
Whoever that may be, it's not the kernel.
Its my understanding that these files should be volatile when they
represent a USB usage, because a USB device can be unplugged instantly and
at any
Linus,
Please pull the latest perf-watchdog-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-watchdog-for-linus
# HEAD: df577149594cefacd62740e86de080c6336d699e watchdog: Fix print-once on
enable
Two small watchdog subsystem fixes.
Thanks,
On 10/12/2014 10:30 AM, Peter Zijlstra wrote:
On Wed, Oct 08, 2014 at 03:37:27PM -0400, r...@redhat.com wrote:
+static void init_numa_topology_type(void)
+{
+ int a, b, c, n;
+
+ n = sched_domains_numa_levels;
+
+ if (n = 1)
+ sched_numa_topology_type =
On Mon, Oct 13, 2014 at 02:22:12PM +0800, Jason Wang wrote:
On 10/12/2014 05:27 PM, Michael S. Tsirkin wrote:
On Sat, Oct 11, 2014 at 03:16:44PM +0800, Jason Wang wrote:
Below should be useful for some experiments Jason is doing.
I thought I'd send it out for early review/feedback.
On 10/12/2014 10:37 AM, Peter Zijlstra wrote:
On Wed, Oct 08, 2014 at 03:37:28PM -0400, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
Preparatory patch for adding NUMA placement on systems with
complex NUMA topology. Also fix a potential divide by zero
in group_weight()
Linus,
Please pull the latest sched-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-core-for-linus
# HEAD: f10e00f4bf360c36edbe6bf18a6c75b171cbe012 sched/dl: Use dl_bw_of()
under rcu_read_lock_sched()
The main changes in this cycle were:
On 10/12/2014 10:53 AM, Peter Zijlstra wrote:
On Wed, Oct 08, 2014 at 03:37:29PM -0400, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
In order to do task placement on systems with complex NUMA topologies,
it is necessary to count the faults on nodes nearby the node that is
being
Linus,
Please pull the latest x86-asm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus
# HEAD: f74954f01ec9bb2004bcc24f247d1f26f1063ad2 x86: Unwind-annotate
thunk_32.S
The changes in this cycle were:
- Speed up the x86
On 10/12/2014 10:56 AM, Peter Zijlstra wrote:
On Wed, Oct 08, 2014 at 03:37:30PM -0400, r...@redhat.com wrote:
+static int preferred_group_nid(struct task_struct *p, int nid)
+{
+ nodemask_t nodes;
+ int hops;
+
+ /* Direct connections between all NUMA nodes. */
+ if
Once again...
On 09/30/2014 07:21 PM, Johann Klammer wrote:
Hello,
After updating the kernel to 3.14.15 I am seeing these messages:
[273684.964081] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273690.020061] saa7146:
Linus,
Please pull the latest x86-boot-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-for-linus
# HEAD: eeeda4cd06e828b331b15741a204ff9f5874d28d x86/relocs: Make
per_cpu_load_addr static
The changes in this cycle were:
- Fix rare SMP-boot
Linus,
Please pull the latest x86-build-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-build-for-linus
# HEAD: 5c630089442c2e3482855c0849fea53abded81e2 x86/kbuild: Eliminate
duplicate command line options
Includes a single commit that simplifies
Linus,
Please pull the latest x86-cleanups-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-cleanups-for-linus
# HEAD: 196cf358422517b3ff3779c46a1f3e26fb084172 x86/tty/serial/8250: Clean
up the asm/serial.h include file a bit
Three small cleanups.
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
# HEAD: 2ed53c0d6cc99fc712f7c037e41d9ec4eb8d6b08 x86/smpboot: Speed up
suspend/resume by avoiding 100ms sleep for CPU offline during S3
This tree
Hi Arnaldo, Borislav,
On 10 October 2014 22:44, Borislav Petkov b...@alien8.de wrote:
On Fri, Oct 10, 2014 at 05:41:58PM -0300, Arnaldo Carvalho de Melo wrote:
Right, stoopid me, no need for some specific tracepoint, just to see
that whatever tp it is, it will show up in rasd's event loop. Ok,
On Mon, Oct 13, 2014 at 05:22:39PM +1030, Rusty Russell wrote:
Michael S. Tsirkin m...@redhat.com writes:
virtio spec 0.9.X requires DRIVER_OK to be set before
VQs are used, but some drivers use VQs before probe
function returns.
Since DRIVER_OK is set after probe, this violates the spec.
Linus,
Please pull the latest x86-cpufeature-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-cpufeature-for-linus
# HEAD: 9298b815efe500b272e4084ed05eeae7a92b5340 x86: Add more disabled
features
This tree includes the following changes:
-
Linus,
Please pull the latest x86-fpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-fpu-for-linus
# HEAD: 6f46b3aef0031c08a7b439d63013dad2aeb093b2 x86: copy_thread: Don't
nullify -ptrace_bps twice
x86 FPU handling fixes, cleanups and enhancements
Linus,
Please pull the latest x86-microcode-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-microcode-for-linus
# HEAD: 44afe6029422da55918d8156c6900dbf5259533b Merge tag
'microcode_cleanups' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: beb9147e95a75f41c984d7235cf6d59f3ca2d5db x86/mm: Update memory map
description to list hypervisor-reserved area
This tree includes the
Changes from v4:
rename virtio_enable_vqs_early() to virtio_device_ready()
Note: Rusty requested we add a BUG_ON in the virtio_ring code.
This can be done by a separate patch on top.
Good for bisectability in case BUG_ON starts triggering :)
Rusty, please review this, and
Replace duplicated code in all transports with a single wrapper in
virtio.c.
The only functional change is in virtio_mmio.c: if a buggy device sends
us an interrupt before driver is set, we previously returned IRQ_NONE,
now we return IRQ_HANDLED.
As this must not happen in practice, this does
On restore, virtio pci does the following:
+ set features
+ init vqs etc - device can be used at this point!
+ set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits
This is in violation of the virtio spec, which
requires the following order:
- ACKNOWLEDGE
- DRIVER
- init vqs
- DRIVER_OK
This
On Sat, Oct 11, 2014 at 09:24:11PM +0530, Vinod Koul wrote:
On Sat, Oct 11, 2014 at 06:21:47PM +0200, Lars-Peter Clausen wrote:
I already send a similar patch a while ago. It is on it's way into 3.18.
I will drop this one then
I did grep the linux-next when I started on this and found no
Now that virtio core ensures config changes don't
arrive during probing, drop config_enable flag
in virtio blk.
On removal, flush is now sufficient to guarantee that
no change work is queued.
This help simplify the driver, and will allow
setting DRIVER_OK earlier without losing config
change
Defer config changed notifications that arrive during
probe/scan/freeze/restore.
This will allow drivers to set DRIVER_OK earlier, without worrying about
racing with config change interrupts.
This change will also benefit old hypervisors (before 2009)
that send interrupts without checking
This is in preparation to extending config changed event handling
in core.
Wrapping these in an API also seems to make for a cleaner code.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Cornelia Huck cornelia.h...@de.ibm.com
---
include/linux/virtio.h | 6 +
virtio spec 0.9.X requires DRIVER_OK to be set before
VQs are used, but some drivers use VQs before probe
function returns.
Since DRIVER_OK is set after probe, this violates the spec.
Even though under virtio 1.0 transitional devices support this
behaviour, we want to make it possible for those
Linus,
Please pull the latest x86-platform-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-platform-for-linus
# HEAD: aece118e487a744eafcdd0c77fe32b55ee2092a1 x86: Add
cpu_detect_cache_sizes to init_intel() add Quark legacy_cache()
The main
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio console violated this
rule by adding inbufs, which causes the VQ to be used directly within
probe.
To fix, call virtio_device_ready before using VQs.
Signed-off-by: Michael S.
config_mutex served two purposes: prevent multiple concurrent config
change handlers, and synchronize access to config_enable flag.
Since commit dbf2576e37da0fcc7aacbfbb9fd5d3de7888a3c1
workqueue: make all workqueues non-reentrant
all workqueues are non-reentrant, and config_enable
is now
From: Paolo Bonzini pbonz...@redhat.com
Michael S. Tsirkin noticed a race condition:
we reset device on freeze, but system WQ is still
running so it might try adding bufs to a VQ meanwhile.
To fix, switch to handling events from the freezable WQ.
Reported-by: Michael S. Tsirkin m...@redhat.com
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after restore returns, virtio net violated this
rule by using receive VQs within restore.
To fix, call virtio_device_ready before using VQs.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by:
Code like
vi-vq = NULL;
kfree(vi)
does not make sense.
Clean it up, use goto error labels for cleanup.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/char/hw_random/virtio-rng.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after restore returns, virtio scsi violated
this rule on restore by kicking event vq within restore.
To fix, call virtio_device_ready before using event queue.
Signed-off-by: Michael S. Tsirkin
Enable VQs early like we do for restore.
This makes it possible to drop the scan callback,
moving scanning into the probe function, and making
code simpler.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/scsi/virtio_scsi.c | 23 +++
1 file changed, 7
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after resume returns, virtio balloon
violated this rule by adding bufs, which causes the VQ to be used
directly within restore.
To fix, call virtio_device_ready before using VQ.
Signed-off-by: Michael S.
Linus,
Please pull the latest x86-ras-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-ras-for-linus
# HEAD: d286c3af48e3ad187fc52a0060c71b0844f234ff x86/mce: Avoid showing
repetitive message from intel_init_thermal()
This tree includes a single
We cancel event work on device removal, but an interrupt
could trigger immediately after this, and queue it
again.
To fix, set a flag.
Loosely based on patch by Paolo Bonzini
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after restore returns, virtio block violated
this rule on restore by restarting queues, which might in theory
cause the VQ to be used directly within restore.
To fix, call virtio_device_ready before using
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after resume returns, virtio console violated this
rule by adding inbufs, which causes the VQ to be used directly within
restore.
To fix, call virtio_device_ready before using VQs.
Signed-off-by: Michael S.
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, but virtio 9p device
adds self to channel list within probe, at which point VQ can be
used in violation of the spec.
To fix, call virtio_device_ready before using VQs.
Signed-off-by:
In the extremely unlikely event that driver initialization fails after
RX buffers are added, virtio net frees RX buffers while VQs are
still active, potentially causing device to use a freed buffer.
To fix, reset device first - same as we do on device removal.
Signed-off-by: Michael S. Tsirkin
We currently kick event within virtscsi_init,
before host is fully initialized.
This can in theory confuse guest if device
consumes the buffers immediately.
To fix, move virtscsi_kick_event_all out to scan/restore.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
goto done;
done:
return;
is ugly, it was put there to make diff review easier.
replace by open-coded return.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Acked-by: Cornelia Huck cornelia.h...@de.ibm.com
---
drivers/net/virtio_net.c | 6 ++
1 file changed, 2
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio net violated this
rule by using receive VQs within probe.
To fix, call virtio_device_ready before using VQs.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by:
Now that virtio core ensures config changes don't arrive during probing,
drop config_enable flag in virtio net.
On removal, flush is now sufficient to guarantee that no change work is
queued.
This help simplify the driver, and will allow setting DRIVER_OK earlier
without losing config change
config_mutex served two purposes: prevent multiple concurrent config
change handlers, and synchronize access to config_enable flag.
Since commit dbf2576e37da0fcc7aacbfbb9fd5d3de7888a3c1
workqueue: make all workqueues non-reentrant
all workqueues are non-reentrant, and config_enable
is now
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio block violated this
rule by calling add_disk, which causes the VQ to be used directly within
probe.
To fix, call virtio_device_ready before using VQs.
Signed-off-by: Michael S.
Linus,
Please pull the latest x86-seccomp-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-seccomp-for-linus
# HEAD: 1dcf74f6edfc3a9acd84d83d8865dd9e2a3b1d1e x86_64, entry: Use
split-phase syscall_trace_enter for 64-bit syscalls
This tree includes
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 4ea48a01bb1a99f4185b77cd90cf962730336cc4 x86/build: Add
arch/x86/purgatory/ make generated files to gitignore
Misc smaller fixes that
Linus,
Please pull the latest x86-uv-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-uv-for-linus
# HEAD: 8091c1f8ea2374695c105591179b1269fb5f2fbb x86/apic/uv: Remove
unnecessary #ifdef
This tree includes a single cleanup commit.
Thanks,
On Sat, 2014-10-11 at 12:20 +0600, Rakib Mullick wrote:
BLD (The Barbershop Load Distribution Algorithm) patch for Linux 3.17
I had a curiosity attack, played with it a little.
My little Q6600 box could be describes as being micro-numa, with two
pathetic little nodes connected by the worst
Hi,
2014-10-13 12:25 GMT+09:00 Greg KH gre...@linuxfoundation.org:
On Mon, Oct 13, 2014 at 11:34:25AM +0900, Daeseok Youn wrote:
Re-arrange the functions for removing forward declarations.
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
---
This patch has too many changes for
On Sun, 12 Oct 2014, Rickard Strandqvist
rickard_strandqv...@spectrumdigital.se wrote:
Fixed wrong usage of strncat, switched to strlcpy.
While sending the string size to function to reduce
the potential for misuse in future.
Signed-off-by: Rickard Strandqvist
Linus,
Please pull the latest x86-vdso-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-vdso-for-linus
# HEAD: f12c1f9002d27374fd205f6e692891116ca22272 x86/vdso: Fix vdso2c's
special_pages[] error checking
Includes a single fix to vdso error
This is version 5 of the series that adds support for the ltc2952 powerpath
chip.
I haven't gotten any further comments on the previous run, so here's a small
update.
This series adds a driver for the LTC2952, an external power control chip, which
signals the OS to shut down. Additionally this
From: René Moll li...@r-moll.nl
The LTC2952 allows control over system power using a push button. It also
supports powering down the board from a controller on the board.
If the power button is pushed, the ltc2952 starts a 400ms window to
properly shut down the software. This window can be
From: René Moll li...@r-moll.nl
Signed-off-by: René Moll li...@r-moll.nl
Signed-off-by: Tjerk Hofmeijer tjerk.hofmei...@xsens.com
Signed-off-by: Frans Klaver frans.kla...@xsens.com
---
.../bindings/power/reset/ltc2952-poweroff.txt | 30 ++
1 file changed, 30
Linus,
On Sat, 11 Oct 2014, Sebastian Reichel wrote:
On Sat, Oct 11, 2014 at 07:01:09AM -0400, Linus Torvalds wrote:
On Fri, Oct 10, 2014 at 5:40 AM, Lee Jones lee.jo...@linaro.org wrote:
The following changes since commit
52addcf9d6669fa439387610bc65c92fa0980cef:
Linux
On 10/10/2014 1:07 PM, Sumit Semwal wrote:
Hi,
Why:
While sharing buffers using dma-buf, currently there's no mechanism to let
devices share their memory access constraints with each other to allow for
delayed allocation of backing storage.
This RFC attempts to introduce the idea of
Update the translation tables from cache mode to pgprot values
according to the PAT settings. This enables changing the cache
attributes of a PAT index in just one place without having to change
at the users side.
With this change it is possible to use the same kernel with different
PAT
The x86 architecture offers via the PAT (Page Attribute Table) a way to
specify different caching modes in page table entries. The PAT MSR contains
8 entries each specifying one of 6 possible cache modes. A pte references one
of those entries via 3 bits: _PAGE_PAT, _PAGE_PWT and _PAGE_PCD.
The
With the dynamical mapping between cache modes and pgprot values it is
now possible to use all cache modes via the Xen hypervisor PAT settings
in a pv domain.
All to be done is to read the PAT configuration MSR and set up the
translation tables accordingly.
Signed-off-by: Juergen Gross
At the moment there are a lot of places that handle setting or getting
the page cache mode by treating the pgprot bits equal to the cache mode.
This is only true because there are a lot of assumptions about the setup
of the PAT MSR. Otherwise the cache type needs to get translated into
pgprot bits
On 10/11/2014 11:55 AM, Daniel Vetter wrote:
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
At present, struct device lacks a mechanism of exposing memory
access constraints for the device.
Consequently, there is also no mechanism to share these constraints
while sharing buffers
Hi Valdis,
Thanks for your remark.
Concerning multiple writing in MIPHY_PLL_SBR_1, the writing of the
first 0 it's to be sure there is no previous request.
Then we take account new setting by writing 0x02.
And then we make it 0 to make sure there is no other pending requests.
I added comments
Hi, Miller Cong
Can we merge this patch into kernel mainline? since the independence
between ipv4 and ipv6 is inconsistent even in the latest linux
kernel(3.17-rc7),
that is, the net namespace is independent in ipv6 while it is not in ipv4.
Thanks a lot.
Zhu Yanjun
On 07/30/2014 01:48 AM,
Hi Alexey,
On 10/10/2014 10:31 PM, Alexey Khoroshilov wrote:
It seems struct esd_usb2 dev is not deallocated on disconnect.
The patch adds the deallocation.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov khoroshi...@ispras.ru
---
This patch fixes commit 2dea53bf57783f243c892e99c10c6921e956aa7e,
serial: of-serial: add PM suspend/resume support, which disables
the uart clock on suspend, but also causes a hardware hang on register
access if no_console_suspend command line option is used.
Also, not every of_serial device is
On Fri, Oct 10, 2014 at 05:20:56PM -0700, Stephen Boyd wrote:
On 10/10, Peter De Schrijver wrote:
drivers/clk/tegra/clk-pll.c:732:unsigned long input_rate =
clk_get_rate(clk_get_parent(hw-clk));
drivers/clk/tegra/clk-pll.c:1288:unsigned long input_rate =
Hi Addy,
On Monday 13 October 2014 at 10:44:04, Addy Ke wrote:
As show in I2C specification:
- Standard-mode: the minimum HIGH period of the scl clock is 4.0us
the minimum LOW period of the scl clock is 4.7us
- Fast-mode: the minimum HIGH period of the scl clock is 0.6us
On 10/10/2014 1:07 PM, Sumit Semwal wrote:
Devices sharing buffers using dma-buf could benefit from sharing their
constraints via struct device, and dma-buf framework would manage the
common constraints for all attached devices per buffer.
With that information, we could have a 'generic'
On Mon, Oct 13, 2014 at 04:41:28PM +1100, NeilBrown wrote:
Hi Greg,
please consider these two patches for a future release.
They now have
Reviewed-by: Tejun Heo t...@kernel.org
and I've addressed Tejun's final nits.
Thanks Tejun for your review and comments.
As soon as they
This fixes space related ERROR reports by checkpatch.pl
Generated by $ git ls-files drivers/staging/rtl8188eu/*.[ch] | \
xargs ./scripts/checkpatch.pl -f --fix-inplace --strict --types=SPACING
Already checked by text comparasion
$git diff -w
and binary comparasion of r8188eu.ko
$objdiff diff
On Thu, Sep 25, 2014 at 07:37:50PM -0500, Felipe Balbi wrote:
HI,
On Fri, Sep 26, 2014 at 07:39:34AM +0800, Peter Chen wrote:
On Thu, Sep 25, 2014 at 09:15:53AM -0500, Felipe Balbi wrote:
On Wed, Sep 24, 2014 at 02:23:38PM +0200, Arnd Bergmann wrote:
On Wednesday 24 September 2014
On Thu, 2014-10-09 at 10:40 +0200, Arnd Bergmann wrote:
A recent bug fix to the MSIx handling in vfio added references
to functions that may not be defined if MSI is disabled in the kernel,
resulting in this link error:
drivers/built-in.o: In function `vfio_msi_set_vector_signal':
From: karam.lee karam@lge.com
Recently rw_page block device operation has been added.
This patchset implements rw_page operation for zram block device
and does some clean-up .
I implemented the feature in zram and tested it.
Test bed was the G2, LG electronic mobile device, whtich has
From: karam.lee karam@lge.com
This patch removes an unnecessary parameter(bio)
from zram_bvec_rw() and zram_bvec_read().
zram_bvec_read() doesn't use a bio parameter, so remove it.
zram_bvec_rw() calls a read/write operation not using bio, so a rw parameter
replaces a bio parameter.
From: karam.lee karam@lge.com
This patch implements rw_page operation for zram block device.
Signed-off-by: karam.lee karam@lge.com
---
drivers/block/zram/zram_drv.c | 37 +
1 file changed, 37 insertions(+)
diff --git
On 09/10/14 15:29, Joe.C wrote:
From: Joe.C yingjoe.c...@mediatek.com
Add support to use gic as a parent for stacked irq domain.
Signed-off-by: Joe.C yingjoe.c...@mediatek.com
---
drivers/irqchip/irq-gic.c | 56
---
1 file changed, 48
From: karam.lee karam@lge.com
This patch changes parameter of valid_io_request for common usage.
The purpose of valid_io_request() is to determine if bio request is
valid or not.
This patch use I/O start address and size instead of a BIO parameter
for common usage.
Signed-off-by: karam.lee
1 - 100 of 1006 matches
Mail list logo
