Fredrik Tolf wrote:
> It is worth noting, also, that this seems to be a situation
> introduced somewhere between 2.6.26 and 2.6.32, because I started
> noticing it when I upgraded from Debian 5.0 to 6.0. I've since tried
> it on 3.2.0, 3.5.4 and 3.7.1, and it appears in every version.
> However, I
On Sat, Mar 23, 2013 at 01:57:01PM -0400, Corey Richardson wrote:
> With the attached config, I get the following build failure:
>
> LD init/built-in.o
> drivers/built-in.o:clk-lpt.c:function v4l2_device_unregister: error:
> undefined reference to 'i2c_unregister_device'
I get following wi
Correct spelling typos.
Signed-off-by: Masanari Iida
---
Documentation/DocBook/media/dvb/dvbproperty.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/DocBook/media/dvb/dvbproperty.xml
b/Documentation/DocBook/media/dvb/dvbproperty.xml
index 4a5eaee..31d
fix for incorrect assignment of signed expression to unsigned variable.
Signed-off-by: Kumar Amit Mehta
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c
b/
Dear list,
I've got an mmapped file (a Berkeley DB region file) with an access
pattern such that it gets some 10-40 MBs of dirtied pages a couple of
times per minute. When the VM comes around to flush these pages to disk,
that causes loads of problems. Since the dirty pages are rather
intersp
Hi Linus,
A collection of minor fixes, more EFI variables paranoia
(anti-bricking) plus the ability to disable the pstore either as a
runtime default or completely, due to bricking concerns.
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17
MFD core driver for various variants of Winbond/Nuvoton SuperIO chips.
Signed-off-by: Guenter Roeck
---
drivers/mfd/Kconfig | 22 +++
drivers/mfd/Makefile |1 +
drivers/mfd/w83627hf-core.c | 324 ++
include/linux/mfd/w83627hf.h |
On Fri, Mar 22, 2013 at 4:28 AM, Frank Rowand wrote:
>> I play upstream kernel on Pandaboard A1 frequently, looks not
>> see the failure problem before. Maybe the problem is config dependent.
>>
>> If you may share your config file, I'd like to do the test too.
3.9-rc2-20130314 doesn't have the p
Another week, another -rc. And things haven't calmed down, meaning
that the nice small and calm -rc2 was definitely the outlier so far.
But I'm optimistic, dammit, and I'm going to keep hoping that things
will change, and the upcoming week will be boring and devoid of any
real work what-so-ever.
I
From: Krzysztof Halasa
Date: Sat, 23 Mar 2013 20:35:46 +0100
> ARM core code currently requires coherent DMA mask to be set. Make sure
> we limit PCI devices to 64 MiB while allowing on-chip devices to access
> the whole 4 GiB address space.
>
> This fixes a v3.7+ regression which broke IXP4xx b
From: Kumar Amit Mehta
Date: Sat, 23 Mar 2013 11:52:55 -0700
> fix for incorrect assignment of signed expression to unsigned variable.
>
> Signed-off-by: Kumar Amit Mehta
Returning positive error codes is just as broken as what is there
currently.
These routines should return 0 or 1, the retu
Hi Linus!
Here is the current set of target-pending/master fixes for v3.9-rc4.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
These are mostly minor fixes this time around. The iscsi-target CHAP
big-endian bugfix and bump FD_MAX_SEC
From: Rafael J. Wysocki
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, d
On Saturday, March 23, 2013 09:21:56 PM Pavel Machek wrote:
> On Sat 2013-03-23 14:00:23, Bjørn Mork wrote:
> > "Rafael J. Wysocki" writes:
> > > On Saturday, March 23, 2013 12:40:12 PM Pavel Machek wrote:
> > >> Hi!
> > >>
> > >> pavel@amd:~$ cat /proc/acpi/battery/BAT0/info
> > >> present:
On Saturday, March 23, 2013 09:18:55 AM Yinghai Lu wrote:
> On Sat, Mar 23, 2013 at 5:30 AM, Rafael J. Wysocki wrote:
>
> >>
> >> Attached patch fix the problem. Please fold it into offending patch in
> >> pm/linux-next.
> >
> > I'd actually prefer to apply it as a separate patch, so can you plea
Please forward - I am not on your email list so please CC any email to
"alsa-info.sh"
I am running openSuSE 12.3, KDE4, alsa, pulseaudio, kernel 3.9-rc3 and
flash (very current version)
The sound works except the volume on pavumixer which goes up and down.
and some times not at all.
It is a
MFD core driver for various variants of Winbond/Nuvoton SuperIO chips.
Signed-off-by: Guenter Roeck
---
My variant of an MFD core driver for Winbond chips.
Key differences to Wim's driver
- Uses mfd infrastructure
- Passes enum instead of raw device id to client drivers
- Uses request_muxed_reg
> David Vrabel (1): xen/events: avoid race with raising an event in
unmask_evtchn()
Unless I am looking in the wrong place, this patch is still the same one
that breaks PV on HVM and Xen ARM guests, see:
http://marc.info/?l=xen-devel&m=136377731913034
David is aware of the issue and I think is
Man, it worked!
You saved my life kkk.
Thank you very much!
2013/3/23 Hugh Dickins :
> On Wed, 20 Mar 2013, Eduardo Cruz wrote:
>
>> Hello.
>>
>> I'm trying to remap some kernel static memory to user space using
>> remap_pfn_range.
>> For that, I wrote a module that initializes a devic
On Sat, Mar 23 2013 at 5:08pm -0400,
Mike Snitzer wrote:
> But even after having changed my test to use /dev/sdb for the origin
> device I cannot reproduce the problem you've reported. Do you have any
> further details on how/why the bios are being altered? Are you
> reliably hitting partial
On Sat, Mar 23, 2013 at 10:08 AM, Stefano Stabellini
wrote:
>
> Unless I am looking in the wrong place, this patch is still the same one
> that breaks PV on HVM and Xen ARM guests, see:
Konrad?
I'll hold off on the pull request for now.
Linus
--
To unsubscribe from this list: send
Please forward - I am not on your email list so please CC any email to
"alsa-info.sh"
I am running openSuSE 12.3, KDE4, alsa, pulseaudio, kernel 3.9-rc3 and
flash (very current version)
The sound works except the volume on pavumixer which goes up and down.
and some times not at all.
It is a
On Sat, Mar 23, 2013 at 01:57:42PM +0100, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> > > In 2011 I started something similar but then with the MFD approach in
> > > mind.
> > > Goal was also to clean-up the w836* watchdog drivers and get a clean
> > > driver that
> > > supports all Winbond super-
The EMAC only has one pinset available for muxing, so hopefully, we
cover all cases.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i-a10.dtsi
index a6bd
From: Stefan Roese
The Allwinner A10 has an ethernet controller that seem to be developped
internally by them.
The exact feature set of this controller is unknown, since there is no
public documentation for this IP, and this driver is mostly the one
published by Allwinner that has been heavily c
The Hackberry has a PHY that needs to be powered up through a GPIO, so
we need to use a fixed regulator here.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10-hackberry.dts | 32 +
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a1
From: Stefan Roese
Signed-off-by: Stefan Roese
---
arch/arm/boot/dts/sun4i-a10-cubieboard.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-cubieboard.dts
b/arch/arm/boot/dts/sun4i-a10-cubieboard.dts
index 88e2dc1..9bf4b4f 100644
--- a/arch/arm/boot/d
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i-a10.dtsi
index 03d2b53..a6bd36a 100644
--- a/arch/arm/boot/dts/sun4i-a10.dtsi
+++ b/arch/arm/boot/dts/sun4i-a1
> --- linux.orig/mm/page_alloc.c 2013-03-19 16:09:03.736450861 -0500
> +++ linux/mm/page_alloc.c 2013-03-22 17:07:43.895405617 -0500
> @@ -4161,10 +4161,23 @@ int __meminit __early_pfn_to_nid(unsigne
> {
> unsigned long start_pfn, end_pfn;
> int i, nid;
> + /*
> +
* Eric Wong (normalper...@yhbt.net) wrote:
> Mathieu Desnoyers wrote:
> > * Eric Wong (normalper...@yhbt.net) wrote:
> > > /*
> > > + * ___wfcq_append: append one local queue to another local queue
> > > + *
>
> > __wfcq_append() and ___wfcq_append() are meant to be private to
> > wfcqueue.h. Th
On Wed, 20 Mar 2013, Eduardo Cruz wrote:
> Hello.
>
> I'm trying to remap some kernel static memory to user space using
> remap_pfn_range.
> For that, I wrote a module that initializes a device, which later I
> use mknod, etc.
>
> When I allocate the memory with kmalloc, everything works: (whe
On Fri, Mar 8, 2013 at 5:11 PM, Paul Gortmaker
wrote:
> From: Thomas Gleixner
>
> The early console implementations are the same all over the place. Move
> the print function to kernel/printk and get rid of the copies.
>
> Signed-off-by: Thomas Gleixner
> Cc: Russell King
> Acked-by: Mike Frys
On Sat, Mar 23, 2013 at 01:45:11PM -0700, Kumar amit mehta wrote:
> On Sat, Mar 23, 2013 at 10:56:47PM +0300, Dan Carpenter wrote:
> >
> > The fix for this is more involved. The function prototype should
> > be changed to return an int. The caller should be updated to check
> > for errors.
> >
>
On Fri, Mar 22, 2013 at 10:15:49PM -0700, Darrick J. Wong wrote:
> Interesting ... if I set up this:
> # echo "0 67108864 linear /dev/sda 0" | dmsetup create origin
> And then repeat the test, but using /dev/mapper/origin as the origin instead
> of /dev/sda, the problem goes away.
So that looks l
On Sat, Mar 23 2013 at 1:15am -0400,
Darrick J. Wong wrote:
> On Fri, Mar 22, 2013 at 11:27:16PM -0400, Mike Snitzer wrote:
> > On Fri, Mar 22 2013 at 7:16pm -0400,
> > Darrick J. Wong wrote:
> >
> > > On Fri, Mar 22, 2013 at 06:34:28PM -0400, Mike Snitzer wrote:
> > > > On Fri, Mar 22 2013 a
On Sat, Mar 23, 2013 at 10:56:47PM +0300, Dan Carpenter wrote:
> On Sat, Mar 23, 2013 at 11:52:55AM -0700, Kumar Amit Mehta wrote:
> > fix for incorrect assignment of signed expression to unsigned variable.
> >
>
> This fix isn't right.
>
> > Signed-off-by: Kumar Amit Mehta
> > ---
> > drivers
Mathieu Desnoyers wrote:
> * Eric Wong (normalper...@yhbt.net) wrote:
> > /*
> > + * ___wfcq_append: append one local queue to another local queue
> > + *
> __wfcq_append() and ___wfcq_append() are meant to be private to
> wfcqueue.h. Therefore, the comment above should be removed, since it is
>
On Sat, Mar 23, 2013 at 8:29 AM, Russ Anderson wrote:
> On Fri, Mar 22, 2013 at 08:25:32AM +0100, Ingo Molnar wrote:
>
> When booting on a large memory system, the kernel spends
> considerable time in memmap_init_zone() setting up memory
I'm adding some asm code in arch/ia64/kernel/ivt.S
to gather some memory usage statistics.
>From whatever reason, when I allocate the memory using
kmalloc/vmalloc, my assembly code cashes the machine when I load the
allocated memory.
If I use static allocated memory, the asm code works.
I know t
On Sat 2013-03-23 14:00:23, Bjørn Mork wrote:
> "Rafael J. Wysocki" writes:
> > On Saturday, March 23, 2013 12:40:12 PM Pavel Machek wrote:
> >> Hi!
> >>
> >> pavel@amd:~$ cat /proc/acpi/battery/BAT0/info
> >> present: yes
> >> design capacity: 0 mWh
> >> last full capaci
On Sat, Mar 23, 2013 at 11:52:55AM -0700, Kumar Amit Mehta wrote:
> fix for incorrect assignment of signed expression to unsigned variable.
>
This fix isn't right.
> Signed-off-by: Kumar Amit Mehta
> ---
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c | 20 ++--
> 1 file ch
On Sat, 23 Mar 2013, Linus Torvalds wrote:
> How the heck did you get your *own* email address wrong in your mail
> headers? "tors...@lst.de" bounces,
Of course I had to goof up somehow :(
This is not my everyday mail setup, the configuration is suboptimal,
admittedly. Sorry for the inconveni
On Fri, Mar 22, 2013 at 8:19 PM, Emmanuel Benisty wrote:
>
> I could reproduce it but could you please let me know what would be
> the right tools I should use to catch the original oops?
> This is what I got but I doubt it will be helpful:
> http://i.imgur.com/Mewi1hC.jpg
In this case, I think t
* Eric Wong (normalper...@yhbt.net) wrote:
> With level-triggered epoll, append/enqueue operations to the
> local/locked queues increase performance by avoiding unnecessary atomic
> operations and barriers. These are necessary to avoid performance
> regressions when looping through ep_send_events
ARM core code currently requires coherent DMA mask to be set. Make sure
we limit PCI devices to 64 MiB while allowing on-chip devices to access
the whole 4 GiB address space.
This fixes a v3.7+ regression which broke IXP4xx built-in network devices.
Signed-off-by: Krzysztof Hałasa
Cc:
diff --g
On Tue, Mar 19, 2013 at 10:25 AM, Wanpeng Li wrote:
> Introduce zero-filled pages handler to capture and handle zero pages.
>
> Acked-by: Dan Magenheimer
> Signed-off-by: Wanpeng Li
> ---
> drivers/staging/zcache/zcache-main.c | 26 ++
> 1 files changed, 26 insertions(
Found with pm/linux-next, network device in QEMU/KVM guest does not
work anymore.
Bisected to commit c13085e5
ACPICA: Resource Mgr: Prevent infinite loops in resource walks
That commit will check acpi_resource length strictly.
it cause acpi_set_current_resources return failure and irq for pci
With level-triggered epoll, append/enqueue operations to the
local/locked queues increase performance by avoiding unnecessary atomic
operations and barriers. These are necessary to avoid performance
regressions when looping through ep_send_events and appending many
items to a local queue.
Signed-
fix for incorrect assignment of signed expression to unsigned variable.
Signed-off-by: Kumar Amit Mehta
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c
That kernel crashed today at a stable 32 bit Gentoo Linux.
The screen shot (just a photo, b/c nothing was in the syslog) can be downloaded
here [1].
The last action before I left the machine for a while was to start a user mode
linux
(stale 32 bit Gentoo, kernel v3.9-rc3-324-g5da273) and run tri
On 03/22, Ananth N Mavinakayanahalli wrote:
>
> Some architectures like powerpc have multiple variants of the trap
> instruction. Introduce an additional helper is_trap_insn() for run-time
> handling of non-uprobe traps on such architectures.
Looks fine to me.
I am going to take this into my tree
On 03/23, Anton Arapov wrote:
>
> IIUC, Oleg have stressed that perf and trace events requires
> additional code to leverage the return probes. IOW this patchset
> implements core only and to use it we need to teach the perf about
> rp_handler().
Yes,
> And I don't see why we would need addit
On Sat, Mar 23, 2013 at 07:00:10PM +0100, Andi Kleen wrote:
>
> Hi Linux,
Also I debut on finally making that famous typo too. Sorry.
-Andi
--
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 htt
> That said, making it just a byte sounds more than enough. How deep
> would anybody want to nest it? Do we care?
Byte should be fine. I'll change that.
-Andi
--
a...@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On 03/22, Josh Stone wrote:
>
> On 03/22/2013 08:10 AM, Oleg Nesterov wrote:
> > This looks simple, but probably we need to add the additional "ulong
> > bp_vaddr"
> > argument for rp_handler().
>
> FWIW, in SystemTap we don't currently do anything that would need
> bp_vaddr.
I know. This is not
Hi Linux,
Thanks. Other code/design review would be still appreciated, even
under the current constraints.
> The other comment I have is that since it does touch non-x86 header
> files etc (although not a lot), you really need to talk to the POWER8
> people about naming of the thing. Calling it
With the attached config, I get the following build failure:
LD init/built-in.o
drivers/built-in.o:clk-lpt.c:function v4l2_device_unregister: error:
undefined reference to 'i2c_unregister_device'
This is after a make oldconfig, perhaps a missed dependency in Kconfig?
config-napo.gz
Descr
How the heck did you get your *own* email address wrong in your mail
headers? "tors...@lst.de" bounces, apparently your email address is
"d...@lst.org". Let's see if that bounces..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
On 03/22, Anton Arapov wrote:
>
> @@ -1513,20 +1596,26 @@ static void handler_chain(struct uprobe *uprobe,
> struct pt_regs *regs)
> {
> struct uprobe_consumer *uc;
> int remove = UPROBE_HANDLER_REMOVE;
> + bool prep = false; /* prepare return uprobe, when needed */
> int rc
On Sat, Mar 23, 2013 at 7:38 AM, Torsten Duwe wrote:
>
> EDID spreads some values across multiple bytes; bit-fiddling is needed
> to retrieve these. The current code to parse "detailed timings" has a
> cut&paste error that results in a vsync offset of at most 15 lines
> instead of 63.
Yeah, it cl
On 03/22, Anton Arapov wrote:
>
> @@ -1488,10 +1496,14 @@ static void handler_chain(struct uprobe *uprobe,
> struct pt_regs *regs)
> {
> struct uprobe_consumer *uc;
> int remove = UPROBE_HANDLER_REMOVE;
> + int rc = 0;
>
> down_read(&uprobe->register_rwsem);
> for (u
Greetings all;
Trying to build a working 3.8.3 kernel, on a *buntu 10.04-4 LTS system here
My usual 'makeit' script didn't report any errors at the end, but the end
trace on screen was obviously incomplete.
Adding a few more echo's to the script, and verifying that every line in it
was termina
Sergey Senozhatsky wrote:
> [3.163894] ===
> [3.163895] [ INFO: suspicious RCU usage. ]
> [3.163897] 3.9.0-rc3-next-20130322-dbg-dirty #1 Not tainted
> [3.163898] ---
> [3.163900] fs/eventpoll.c:545 suspicious rcu_derefere
On 03/23/2013 05:30 PM, Thomas Petazzoni wrote:
Dear Sebastian Hesselbarth,
On Sat, 23 Mar 2013 16:25:54 +0100, Sebastian Hesselbarth wrote:
I understand that you proposed patch fixes mvsdio grab mpp0 by accident.
But what if you have a kirkwood board where cd-gpio _is_ connected to mpp0?
It
On Sat, Mar 23, 2013 at 10:16:28AM -0700, Linus Torvalds wrote:
> On Sat, Mar 23, 2013 at 8:52 AM, Borislav Petkov wrote:
> >
> > Really? Let's see:
>
> Your test seems to assume that a single bit is sufficient, which
> sounds unlikely. If you have any kind of nesting going on, you need
> more th
With the LSI FW643 rev 8 [1], the first commanded bus reset at
the conclusion of ohci_enable() has been observed to fail with
the following messages:
[4.884015] firewire_ohci :01:00.0: failed to read phy reg
[5.684012] firewire_ohci :01:00.0: failed to read phy reg
With drive
Signed-off-by: Vincent Stehlé
---
kernel/.gitignore |1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/.gitignore b/kernel/.gitignore
index ab4f109..b3097bd 100644
--- a/kernel/.gitignore
+++ b/kernel/.gitignore
@@ -4,3 +4,4 @@
config_data.h
config_data.gz
timeconst.h
+hz.bc
--
1.7
On Sat, Mar 23, 2013 at 8:52 AM, Borislav Petkov wrote:
>
> Really? Let's see:
Your test seems to assume that a single bit is sufficient, which
sounds unlikely. If you have any kind of nesting going on, you need
more than one bit. Then add/sub isn't a single "xor" of a bit any
more.
That said, m
On Fri, Mar 22, 2013 at 6:24 PM, Andi Kleen wrote:
>
> Some questions and answers:
>
> - How much does it improve performance?
> I cannot share any performance numbers at this point unfortunately.
> Also please keep in mind that the tuning is very preliminary and
> will be revised.
Quite frankly,
On Fri, 22 Mar 2013, Konrad Rzeszutek Wilk wrote:
> Hey Linus,
>
> Please git pull the following tag:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> stable/for-linus-3.9-rc3-tag
>
> which is full of fixes. The signed tag has the details (as always) but
> this is mostly just
If the kernel was booted with the "quiet" boot option we have currently no
chance to see why an initrd failes.
Change KERN_WARNING to KERN_ERR to see what is going on.
Signed-off-by: Richard Weinberger
---
init/main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/init
Dear Sebastian Hesselbarth,
On Sat, 23 Mar 2013 16:25:54 +0100, Sebastian Hesselbarth wrote:
> I understand that you proposed patch fixes mvsdio grab mpp0 by accident.
> But what if you have a kirkwood board where cd-gpio _is_ connected to mpp0?
It didn't work with the existing mvsdio driver, so
On Sat, Mar 23, 2013 at 04:52:56PM +0100, Borislav Petkov wrote:
> And wow, the XOR is *actually* faster. That's whopping three cycles on
> AMD. Similar observation on SNB.
Ok, correction: I was looking at the wrong row in the table. The XOR
version with an immediate and mem access is actually as
Looks good to me.
--
Matthew Garrett | mj...@srcf.ucam.org
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
On Sat, Mar 23, 2013 at 5:30 AM, Rafael J. Wysocki wrote:
>>
>> Attached patch fix the problem. Please fold it into offending patch in
>> pm/linux-next.
>
> I'd actually prefer to apply it as a separate patch, so can you please post
> it with a proper changelog?
but that will break bisecting, ri
On 03/22/2013 04:23 PM, Naoya Horiguchi wrote:
When we have a page fault for the address which is backed by a hugepage
under migration, the kernel can't wait correctly until the migration
finishes. This is because pte_offset_map_lock() can't get a correct
migration entry for hugepage. This patch
On Sat, Mar 23, 2013 at 02:51:56PM +0100, Andi Kleen wrote:
> Bit fields are slower and larger in code and unlike the others this is
> on hot paths.
Really? Let's see:
unsigned:
=
.file 8 "/w/kernel/linux-2.6/arch/x86/include/asm/thread_info.h"
.loc 8 211 0
#APP
# 211 "/w
On Fri, Mar 22, 2013 at 08:25:32AM +0100, Ingo Molnar wrote:
>
> * David Rientjes wrote:
>
> > On Thu, 21 Mar 2013, Ingo Molnar wrote:
> >
> > > > Index: linux/mm/page_alloc.c
> > > > ===
> > > > --- linux.orig/mm/page_alloc.c 201
On 03/23/2013 04:17 PM, Thomas Petazzoni wrote:
On Sat, 23 Mar 2013 13:56:58 +0100, Sebastian Hesselbarth wrote:
mvsdio_platform_data allows to pass card detect and write protect gpio
numbers to the driver. Some kirkwood boards don't use both pins as
they are not connected, and don't set the cor
Dear Sebastian Hesselbarth,
On Sat, 23 Mar 2013 13:56:58 +0100, Sebastian Hesselbarth wrote:
> mvsdio_platform_data allows to pass card detect and write protect gpio
> numbers to the driver. Some kirkwood boards don't use both pins as
> they are not connected, and don't set the corresponding value
On Sat, 2013-03-23 at 18:42 +0800, zhangwei(Jovi) wrote:
> Do I need to resend this patch based on your new work?(and testing) to make
> you can merge this patch easily.
>
Yes please,
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
The CPU used in Marvell Dove SoCs is a PJ4 Sheeva core. Using
CONFIG_CPU_PJ4 instead of CONFIG_CPU_V7 will also allow to enable
iWMMXt extensions on Dove.
Signed-off-by: Sebastian Hesselbarth
---
Cc: Russell King
Cc: Jason Cooper
Cc: Andrew Lunn
Cc: linux-arm-ker...@lists.infradead.org
Cc: lin
This patch adds a common clock driver for Silicon Labs Si5351a/b/c
i2c programmable clock generators. Currently, the driver supports
DT kernels only and VXCO feature of si5351b is not implemented. DT
bindings selectively allow to overwrite stored Si5351 configuration
which is very helpful for clock
When KMS has parsed an EDID "detailed timing", it leaves the frame
rate zeroed. Consecutive (debug-) output of that mode thus yields 0
for vsync. This simple fix also speeds up future invocations of
drm_mode_vrefresh(). While it is debatable whether this qualifies
as a -stable fix I'd apply it for
Hi all,
I'm describing a PAL CRT to my HTPC. Since it uses a 50Hz frame
rate, I had to use a "detailed timing" entry when I crafted an EDID
blob. User space tools properly reproduce the mode line I used
originally, but the kernel gets the vsync position and the frame
rate wrong. Fixes follow.
EDID spreads some values across multiple bytes; bit-fiddling is needed
to retrieve these. The current code to parse "detailed timings" has a
cut&paste error that results in a vsync offset of at most 15 lines
instead of 63. en.wikipedia.org/wiki/EDID "detailed timing" bytes
10+11 show why that need
The of_device_id table is supposed to be zero-terminated.
Signed-off-by: Axel Lin
---
drivers/clocksource/exynos_mct.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
index 203ac05..3cdafc0 100644
--- a/drivers/clocksourc
From: Rafael J. Wysocki
It turns out that _Lxx control methods provided by some BIOSes clear
the PME Status bit of PCI devices they handle, which means that
pci_acpi_wake_dev() cannot really use that bit to check whether or
not the device has signalled wakeup.
For this reason, make pci_acpi_wake
On 3/23/2013 3:23 AM, Henrik Austad wrote:
> + /* we don't have to disable preemptions here as each core has the same
> + * clock-frequency */
Looks OK except the comment is in the wrong style. Kernel multiline comments
/*
* Should look
* like this.
*/
and use full sentences with pu
Add hot cpu notifier to reset the request virtqueue affinity
when doing cpu hotplug.
Cc: linux-s...@vger.kernel.org
Signed-off-by: Paolo Bonzini
Signed-off-by: Wanlong Gao
Reviewed-by: Asias He
---
drivers/scsi/virtio_scsi.c | 29 +
1 file changed, 29 insertions(+)
virtio_scsi_target_state is now empty. We will find new uses for it in
the next few patches, so this patch does not drop it completely.
And as James suggested, we use entries target_alloc and target_destroy
in the host template to allocate and destroy the virtio_scsi_target_state
of each target,
On 03/23/2013 02:36 PM, Paolo Bonzini wrote:
> Il 20/03/2013 08:56, Wanlong Gao ha scritto:
>>> This one does not apply on top of virtio-next + patch 1-4 in this series.
>>
>> I'm very sorry.
>>
>> This fault is because I modified the 4/5 from
>> "/* if the affinity hint is set for virtqueues */"
From: Paolo Bonzini
This patch adds queue steering to virtio-scsi. When a target is sent
multiple requests, we always drive them to the same queue so that FIFO
processing order is kept. However, if a target was idle, we can choose
a queue arbitrarily. In this case the queue is chosen according
From: Paolo Bonzini
This will be needed soon in order to retrieve the per-target
struct.
Cc: linux-s...@vger.kernel.org
Signed-off-by: Paolo Bonzini
Signed-off-by: Wanlong Gao
Reviewed-by: Asias He
---
drivers/scsi/virtio_scsi.c | 17 +
1 file changed, 9 insertions(+), 8 dele
From: Paolo Bonzini
Avoid duplicated code in all of the callers.
Cc: linux-s...@vger.kernel.org
Signed-off-by: Paolo Bonzini
Signed-off-by: Wanlong Gao
Reviewed-by: Asias He
---
drivers/scsi/virtio_scsi.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
diff --g
This series implements virtio-scsi queue steering, which gives
performance improvements of up to 50% (measured both with QEMU and
tcm_vhost backends).
This version rebased on Rusty's virtio ring rework patches, which
has already gone into virtio-next today.
We hope this can go into virtio-next tog
>
> This surely can be a bitfield like the other two below. It is basically
> begging to be one.
Bit fields are slower and larger in code and unlike the others this is on hot
paths.
-Andi
--
a...@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsub
From: Samu Kallio
In paravirtualized x86_64 kernels, vmalloc_fault may cause an oops
when lazy MMU updates are enabled, because set_pgd effects are being
deferred.
One instance of this problem is during process mm cleanup with memory
cgroups enabled. The chain of events is as follows:
- zap_pte
From: Boris Ostrovsky
Invoking arch_flush_lazy_mmu_mode() results in calls to
preempt_enable()/disable() which may have performance impact.
Since lazy MMU is not used on bare metal we can patch away
arch_flush_lazy_mmu_mode() so that it is never called in such
environment.
Signed-off-by: Boris
On Sat, 23 Mar 2013 10:41:56 +, Russell King - ARM Linux wrote:
> Please look at how IORESOURCE_* stuff is defined:
> #define IORESOURCE_TYPE_BITS0x1f00 /* Resource type */
> #define IORESOURCE_IO 0x0100 /* PCI/ISA I/O ports */
> #define IORESOURCE_MEM
1 - 100 of 134 matches
Mail list logo
