Re: sysfs permissions on dynamic attributes (led delay_on and delay_off)

On Fri, Jul 20, 2012 at 9:08 PM, Greg KH wrote: > On Fri, Jul 20, 2012 at 05:46:14PM -0700, Colin Cross wrote: >> I'm trying to use the standard ledtrig-timer.c code to handle led >> blinking for notifications on an Android device, and I'm hitting some >> issues with setting permissions on the

Re: [RFC] firmware load: defer request_firmware during early boot and resume

CC guys who discussed the problem in the below link in Jan. : http://marc.info/?t=13252895602=10=2 On Fri, Jul 20, 2012 at 8:33 PM, Ming Lei wrote: > The RFC patch is just for discussing if the idea of deferring > request_firmware is doable for addressing the issue of >

Re: sysfs permissions on dynamic attributes (led delay_on and delay_off)

On Fri, Jul 20, 2012 at 05:46:14PM -0700, Colin Cross wrote: > I'm trying to use the standard ledtrig-timer.c code to handle led > blinking for notifications on an Android device, and I'm hitting some > issues with setting permissions on the dynamically created delay_on > and delay_off attributes.

[PATCH 18/19] kprobes: introduce ftrace based optimization

From: Masami Hiramatsu Introduce function trace based kprobes optimization. With using ftrace optimization, kprobes on the mcount calling address, use ftrace's mcount call instead of breakpoint. Furthermore, this optimization works with preemptive kernel not like as current jump-based

[PATCH 14/19] kprobes: Inverse taking of module_mutex with kprobe_mutex

From: Steven Rostedt Currently module_mutex is taken before kprobe_mutex, but this can cause issues when we have kprobes register ftrace, as the ftrace mutex is taken before enabling a tracepoint, which currently takes the module mutex. If module_mutex is taken before kprobe_mutex, then we can

[PATCH 13/19] ftrace: add ftrace_set_filter_ip() for address based filter

From: Masami Hiramatsu Add a new filter update interface ftrace_set_filter_ip() to set ftrace filter by ip address, not only glob pattern. Link: http://lkml.kernel.org/r/20120605102808.27845.67952.stgit@localhost.localdomain Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc:

[PATCH 08/19] ftrace/x86: Remove function_trace_stop check from graph caller

From: Steven Rostedt The graph caller is called by the mcount callers, which already does the check against the function_trace_stop variable. No reason to check it again. Link: http://lkml.kernel.org/r/20120711195745.588538...@goodmis.org Signed-off-by: Steven Rostedt ---

[PATCH 17/19] ftrace: Make ftrace_location() a nop on !DYNAMIC_FTRACE

From: Steven Rostedt When CONFIG_DYNAMIC_FTRACE is not set, ftrace_location() is not defined. If a user (like kprobes) references this function, it will break the compile when CONFIG_DYNAMIC_FTRACE is not set. Add ftrace_location() as a nop (return 0) when DYNAMIC_FTRACE is not defined. Link:

[PATCH 07/19] ftrace/x86_32: Simplify parameter setup for ftrace_regs_caller

From: Uros Bizjak The final position of the stack after saving regs and setting up the parameters for ftrace_regs_call, is the position of the pt_regs needed for the 4th parameter. Instead of saving it into a temporary reg and pushing the reg, simply push the stack pointer. Link:

[PATCH 09/19] ftrace: Add default recursion protection for function tracing

From: Steven Rostedt As more users of the function tracer utility are being added, they do not always add the necessary recursion protection. To protect from function recursion due to tracing, if the callback ftrace_ops does not specifically specify that it protects against recursion (by setting

[PATCH 12/19] ftrace: Add selftest to test function save-regs support

From: Steven Rostedt Add selftests to test the save-regs functionality of ftrace. If the arch supports saving regs, then it will make sure that regs is at least not NULL in the callback. If the arch does not support saving regs, it makes sure that the registering of the ftrace_ops that

[PATCH 10/19] ftrace: Only compile ftrace selftest if selftests are enabled

From: Steven Rostedt No need to compile in the ftrace selftest helper file if selftests are not being executed. Signed-off-by: Steven Rostedt --- kernel/trace/Makefile |2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/trace/Makefile b/kernel/trace/Makefile index b831087..8370908

[PATCH 16/19] kprobes: Move locks into appropriate functions

From: Masami Hiramatsu Break a big critical region into fine-grained pieces at registering kprobe path. This helps us to solve circular locking dependency when introducing ftrace-based kprobes. Link: http://lkml.kernel.org/r/20120605102826.27845.81689.stgit@localhost.localdomain Cc: Thomas

[PATCH 15/19] kprobes: cleanup to separate probe-able check

From: Masami Hiramatsu Separate probe-able address checking code from register_kprobe(). Link: http://lkml.kernel.org/r/20120605102820.27845.90133.stgit@localhost.localdomain Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Ananth N Mavinakayanahalli Cc: "Frank Ch. Eigler"

[PATCH 06/19] ftrace/x86: Add save_regs for i386 function calls

From: Steven Rostedt Add saving full regs for function tracing on i386. The saving of regs was influenced by patches sent out by Masami Hiramatsu. Link: Link: http://lkml.kernel.org/r/20120711195745.379060...@goodmis.org Reviewed-by: Masami Hiramatsu Signed-off-by: Steven Rostedt ---

[PATCH 04/19] ftrace/x86_32: Push ftrace_ops in as 3rd parameter to function tracer

From: Steven Rostedt Add support of passing the current ftrace_ops into the 3rd parameter of the callback to the function tracer. Link: http://lkml.kernel.org/r/20120612225424.942411...@goodmis.org Reviewed-by: Masami Hiramatsu Signed-off-by: Steven Rostedt --- arch/x86/include/asm/ftrace.h

[PATCH 11/19] ftrace: Add selftest to test function trace recursion protection

From: Steven Rostedt Add selftests to test the function tracing recursion protection actually does work. It also tests if a ftrace_ops states it will perform its own protection. Although, even if the ftrace_ops states it will protect itself, the ftrace infrastructure may still provide protection

[PATCH 02/19] ftrace: Consolidate arch dependent functions with list function

From: Steven Rostedt As the function tracer starts to get more features, the support for theses features will spread out throughout the different architectures over time. These features boil down to what each arch does in the mcount trampoline (the ftrace_caller). Currently there's two features

[PATCH 03/19] ftrace: Return pt_regs to function trace callback

From: Steven Rostedt Return as the 4th paramater to the function tracer callback the pt_regs. Later patches that implement regs passing for the architectures will require having the ftrace_ops set the SAVE_REGS flag, which will tell the arch to take the time to pass a full set of pt_regs to the

[PATCH 01/19] ftrace: Pass ftrace_ops as third parameter to function trace callback

From: Steven Rostedt Currently the function trace callback receives only the ip and parent_ip of the function that it traced. It would be more powerful to also return the ops that registered the function as well. This allows the same function to act differently depending on what ftrace_ops

[PATCH 05/19] ftrace/x86: Add separate function to save regs

From: Steven Rostedt Add a way to have different functions calling different trampolines. If a ftrace_ops wants regs saved on the return, then have only the functions with ops registered to save regs. Functions registered by other ops would not be affected, unless the functions overlap. If one

[PATCH 19/19] kprobes/x86: ftrace based optimization for x86

From: Masami Hiramatsu Add function tracer based kprobe optimization support handlers on x86. This allows kprobes to use function tracer for probing on mcount call. Link: http://lkml.kernel.org/r/20120605102838.27845.26317.stgit@localhost.localdomain Cc: Thomas Gleixner Cc: Ingo Molnar Cc:

[PATCH 00/19] [GIT PULL][v3.6] ftrace: Allow kprobes to work with ftace

Ingo, This patch series extends ftrace function tracing utility to be more dynamic for its users. It allows for data passing to the callback functions, as well as reading regs as if a breakpoint were to trigger at function entry. The main goal of this patch series was to allow kprobes to use

[PATCH 1/2] ARM: vt8500: Update vt8500-ehci driver to support device tree.

Signed-off-by: Tony Prisk --- .../devicetree/bindings/usb/vt8500-ehci.txt| 10 ++ drivers/usb/host/ehci-vt8500.c |9 + 2 files changed, 19 insertions(+), 0 deletions(-) create mode 100644 Documentation/devicetree/bindings/usb/vt8500-ehci.txt

[PATCHv3 2/2] ARM: vt8500: Add support for UHCI companion controller

Add support for a generic non-pci UHCI companion controller. Existing board files for arch-vt8500 updated to include UHCI support. Signed-off-by: Tony Prisk --- V3: Added the missing commits for the board files. arch/arm/mach-vt8500/bv07.c |1 +

Re: [PATCH] dmi: Feed DMI table to /dev/random driver

On Fri, Jul 20, 2012 at 06:19:33PM -0700, Tony Luck wrote: > On Fri, Jul 20, 2012 at 5:56 PM, Theodore Ts'o wrote: > > The other approach was to add some new interface that random.c would > > call which would grab the dmi data from rand_initialize(). But that's > > going to be a lot more

Re: [PATCH] dmi: Feed DMI table to /dev/random driver

On Fri, Jul 20, 2012 at 5:56 PM, Theodore Ts'o wrote: > The other approach was to add some new interface that random.c would > call which would grab the dmi data from rand_initialize(). But that's > going to be a lot more complicated, so I guess we should go with the > simple/stupid approach.

Re: [PATCH RESEND 5/5] vhost-blk: Add vhost-blk support

On 07/21/2012 04:56 AM, Anthony Liguori wrote: "Michael S. Tsirkin" writes: On Thu, Jul 19, 2012 at 08:05:42AM -0500, Anthony Liguori wrote: Of course, the million dollar question is why would using AIO in the kernel be faster than using AIO in userspace? Actually for me a more important

Re: [PATCH] dmi: Feed DMI table to /dev/random driver

On Fri, Jul 20, 2012 at 01:15:20PM -0700, Tony Luck wrote: > Send the entire DMI (SMBIOS) table to the /dev/random driver to > help seed its pools. > > Signed-off-by: Tony Luck > --- > > This looks a useful addition to your /dev/random series. There are > lots of platform specific goodies in

Re: ibmveth bug?

On Fri, 2012-07-20 at 15:41 -0700, Nishanth Aravamudan wrote: > Ping on this ... we've tripped the same issue on a different system, it > would appear. Would appreciate if anyone can provide answers to the > questions below. Well, I haven't hit it but your description makes sense. Why not use

Re: [PATCHv3 0/6] tun zerocopy support

From: "Michael S. Tsirkin" Date: Fri, 20 Jul 2012 22:23:03 +0300 > Same as with macvtap, I get single-percentage wins in CPU utilization > on guest to external from this patchset, and a performance regression on > guest to host, so more work is needed until this feature can move out of >

Re: [PATCH] MPILIB: Provide count_leading/trailing_zeros() based on arch functions

From: David Howells Date: Fri, 20 Jul 2012 15:21:39 +0100 > Arnd Bergmann wrote: > >> I don't generally like to put stuff into asm-generic when it's unlikely >> to be overridden by architectures. It would really belong into >> include/linux, but then again we have all the other bitops in

sysfs permissions on dynamic attributes (led delay_on and delay_off)

I'm trying to use the standard ledtrig-timer.c code to handle led blinking for notifications on an Android device, and I'm hitting some issues with setting permissions on the dynamically created delay_on and delay_off attributes. For most sysfs files, we have userspace uevent parser that watches

[PATCH 4/4] kdb: Switch to nolock variants of kmsg_dump functions

The locked variants are prone to deadlocks (suppose we got to the debugger w/ the logbuf lock held), so let's switch to nolock variants. Signed-off-by: Anton Vorontsov --- kernel/debug/kdb/kdb_main.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 3/4] printk: Implement some unlocked kmsg_dump functions

If used from KDB, the locked variants are prone to deadlocks (suppose we got to the debugger w/ the logbuf lock held). So, we have to implement a few routines that grab no logbuf lock. Yet we don't need these functions in modules, so we don't export them. Signed-off-by: Anton Vorontsov ---

[PATCH 2/4] printk: Remove kdb_syslog_data

The function is no longer needed, so remove it. Signed-off-by: Anton Vorontsov --- kernel/debug/kdb/kdb_private.h |1 - kernel/printk.c| 15 --- 2 files changed, 16 deletions(-) diff --git a/kernel/debug/kdb/kdb_private.h b/kernel/debug/kdb/kdb_private.h index

[PATCH for-3.5 1/4] kdb: Revive dmesg command

dmesg command appears to be broken after the printk rework. The old logic in kdb code makes no sense in terms of current printk/logging storage format, and KDB simply hangs forever. This patch revives the command by switching to kmsg_dumper iterator. The code is now much more simpler and

[PATCH 0/4] KDB: Fix dmesg command

Hi all, The dmesg command appears to be broken after the printk rework. The old logic in the kdb code makes no sense in terms of current printk/logging storage format, and KDB simply hangs forever upon entering 'dmesg' command. The first patch revives the command by switching to kmsg_dumper

Re: [PATCH 5/5] perf gtk/browser: Use hist_period_print functions

On Fri, Jul 20, 2012 at 10:43 PM, Pekka Enberg wrote: > On Thu, Jul 19, 2012 at 6:42 PM, Namhyung Kim wrote: >> Now we can support color using pango markup with this change. >> >> Signed-off-by: Namhyung Kim > > Can you please CC me on perf GTK patches? > Sorry, I'll do that in the future. :)

[tip:x86/efi] x86, efi: Handover Protocol

Commit-ID: 9ca8f72a9297f2052d806bde176533aa69bd Gitweb: http://git.kernel.org/tip/9ca8f72a9297f2052d806bde176533aa69bd Author: Matt Fleming AuthorDate: Thu, 19 Jul 2012 10:23:48 +0100 Committer: H. Peter Anvin CommitDate: Fri, 20 Jul 2012 16:18:58 -0700 x86, efi: Handover

Re: perf with precise attribute kills all KVM based VMs

On 7/9/12 8:47 AM, Peter Zijlstra wrote: On Mon, 2012-07-09 at 17:39 +0300, Avi Kivity wrote: Disabling PEBS events for guests isn't pretty though.. We already have atomic MSR switching at guest entry/exit time. So it's not pretty in terms of not getting full profiling, but the code won't be

Re: perf with precise attribute kills all KVM based VMs

On 7/11/12 1:10 AM, Gleb Natapov wrote: Looks like Avi is right about the overshoot. Can you test something like this? diff --git a/arch/x86/kernel/cpu/perf_event_intel.c b/arch/x86/kernel/cpu/perf_event_intel.c index 166546e..5fb371a 100644 --- a/arch/x86/kernel/cpu/perf_event_intel.c +++

[PATCH RFT] net: Change niu_rbr_fill() to use unlikely() to check niu_rbr_add_page() return value

Change niu_rbr_fill() to use unlikely() to check niu_rbr_add_page() return value to be consistent with the rest of the checks after niu_rbr_add_page() calls in this file. Signed-off-by: Shuah Khan --- drivers/net/ethernet/sun/niu.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

mmotm 2012-07-20-16-30 uploaded

The mm-of-the-moment snapshot 2012-07-20-16-30 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH 02/11] perf kvm: set name for VM process in guest machine

COMM events are not generated in the context of a guest machine, so the thread name is never set for the VMM process. For example, the qemu-kvm name applies to the process in the host machine, not the guest machine. So, samples for guest machines are currently displayed as: 99.67% :5671

[PATCH 06/11] perf kvm: limit repetitive guestmount message to once per directory

After 7ed97ad use of the guestmount option without a subdir for *each* VM generates an error message for each sample related to that VM. Once per VM is enough. Signed-off-by: David Ahern Cc: Arnaldo Carvalho de Melo Cc: Ingo Molnar Cc: Jiri Olsa Cc: Namhyung Kim Cc: Frederic Weisbecker Cc:

[PATCH 07/11] perf tools: dump exclude_{guest,host}, precise_ip header info too

Adds the attributes to the event line in the header dump. From: event : name = cycles, type = 0, config = 0x0, config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, ... to event : name = cycles, type = 0, config = 0x0, config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0,

[PATCH 03/11] perf kvm: guest userspace samples should not be lumped with host uspace

e.g., perf kvm --host --guest report -i perf.data --stdio -D shows: 1 599127912065356 0x143b8 [0x48]: PERF_RECORD_SAMPLE(IP, 5): 5671/5676: 0x7fdf95a061c0 period: 1 addr: 0 ... chain: nr:2 . 0: ff80 . 1: fe00 ... thread: qemu-kvm:5671 .. dso: (IP, 5)

[PATCH 00/11] perf tool: assorted cleanups and bug fixes

Arnaldo: Welcome back from vacation. Some cleanups and bug fixes for 3.6. Patch 8 should apply to stable if Gleb's and Peter's patches are backported as well. David Ahern (11): perf tool: add machine id to modules debug message perf kvm: set name for VM process in guest machine perf kvm:

[PATCH 08/11] perf tool: precise mode requires exclude_guest

PEBS cannot be used with guest mode. If user adds :p modifier set exclude_guest as well. Signed-off-by: David Ahern Cc: Arnaldo Carvalho de Melo Cc: Ingo Molnar Cc: Jiri Olsa Cc: Namhyung Kim Cc: Frederic Weisbecker Cc: Peter Zijlstra Cc: Gleb Natapov Link:

[PATCH 09/11] perf top: error handling for counter creation should parallel perf-record

5a7ed29 fixed up perf-record but not perf-top. Similar argument holds for it -- fallback to PMU only if it does not exist and handle invalid attributes separately. Signed-off-by: David Ahern Cc: Arnaldo Carvalho de Melo Cc: Ingo Molnar Cc: Jiri Olsa Cc: Namhyung Kim Cc: Frederic Weisbecker

[PATCH 11/11] perf kvm top: limit guest kernel info message to once

'perf kvm top' shows a continual flurry of: Can't find guest [5201]'s kernel information if it can't find the guest info and with a lot of VMs running a user has no chance of reading them all. Limit message to once per guest. Signed-off-by: David Ahern Cc: Arnaldo Carvalho de Melo Cc: Ingo

[PATCH 10/11] perf tool: give user better message if precise is not supported

If the PEBS is not supported (e.g., a VM) and the precise modifier is set the user is given a confusing error message: $ perf top -e cycles:p The sys_perf_event_open() syscall returned with 95 (Operation not supported). /bin/dmesg may provide additional information. No CONFIG_PERF_EVENTS=y

[PATCH 05/11] perf kvm: use strtol for walking guestmount directory

Signed-off-by: David Ahern Cc: Arnaldo Carvalho de Melo Cc: Ingo Molnar Cc: Jiri Olsa Cc: Namhyung Kim Cc: Frederic Weisbecker Cc: Peter Zijlstra --- tools/perf/util/symbol.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/tools/perf/util/symbol.c

[PATCH 04/11] perf kvm: fix bug resolving guest kernel syms - v2

Guest kernel symbols are not resolved despite passing the information needed to resolve them. e.g., perf kvm --guest --guestmount=/tmp/guest-mount record -a -- sleep 1 perf kvm --guest --guestmount=/tmp/guest-mount report --stdio 36.55% [guest/11399] [unknown] [g]

[PATCH 01/11] perf tool: add machine id to modules debug message

Current debug message is: Problems creating module maps, continuing anyway... When running multiple VMs it would be nice to know which machine the message is referring to: $ perf kvm --guest --guestmount=/tmp/guest-mount record -av -- sleep 10 Problems creating module maps for guest 6613,

Re: [PATCH] forcedeth: spin_unlock_irq in interrupt handler fix

From: Denis Efremov Date: Sat, 21 Jul 2012 01:54:34 +0400 > The replacement of spin_lock_irq/spin_unlock_irq pair in interrupt > handler by spin_lock_irqsave/spin_lock_irqrestore pair. > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Denis Efremov

Re: linux-next: manual merge of the staging tree with the target-merge tree

Hi Greg, On Fri, 2012-07-20 at 21:42 +0300, Michael S. Tsirkin wrote: > On Fri, Jul 20, 2012 at 11:03:58AM -0700, Greg KH wrote: > > On Fri, Jul 20, 2012 at 10:52:58AM -0700, Nicholas A. Bellinger wrote: > > > Hi Greg, > > > > > > This was a request from MST (CC'ed) in order to have TCM_VHOST

Re: oops in kernel ( 3.4.x -> 3.5rc )

Well done 1fd36adcd98c14d2fd97f545293c488775cb2823 : the bug occurs ( cf dump ) 1dce27c5aa6770e9d195f2bb7db1db3d4dde5591 : the bug not occurs Regards, Nicolas Prochazka. dump / 1fd36adcd98c14d2fd97f545293c488775cb2823 lloc_fd: slot 71 not NULL! alloc_fd: slot 71 not NULL! alloc_fd: slot 71

gateway icmp redirect handling problem (3.0.36-3.0.23)

Hello, I'm experiencing the following problem with kernel versions 3.0.36 (down to 3.0.23): on our network we all have one default gateway, it's 10.1.1.254, but there are some networks for which we have another gateway and for this networks the default gateway sends an icmp redirect. lets

Re: [PATCH] Shorten constant names for EFI variable attributes

On 07/20/2012 04:34 PM, H. Peter Anvin wrote: On 07/20/2012 03:30 PM, Khalid Aziz wrote: This patch is based upon earlier discussion at . You are right that EFI specification uses exactly these long names for the constants, but does that mean kernel must

Re: ibmveth bug?

Ping on this ... we've tripped the same issue on a different system, it would appear. Would appreciate if anyone can provide answers to the questions below. Thanks, Nish On 15.05.2012 [10:01:41 -0700], Nishanth Aravamudan wrote: > Hi Santiago, > > Are you still working on ibmveth? > > I've

Re: [PATCH] Shorten constant names for EFI variable attributes

On 07/20/2012 03:30 PM, Khalid Aziz wrote: On 07/20/2012 04:10 PM, H. Peter Anvin wrote: On 07/20/2012 03:08 PM, Khalid Aziz wrote: Replace very long constants for EFI variable attributes with shorter and more convenient names. Also create an alias for the current longer names so as to not

[tip:x86/mm] x86/tlb: Fix build warning and crash when building for !SMP

Commit-ID: 7efa1c87963d23cc57ba40c07316d3e28cc75a3a Gitweb: http://git.kernel.org/tip/7efa1c87963d23cc57ba40c07316d3e28cc75a3a Author: Alex Shi AuthorDate: Fri, 20 Jul 2012 09:18:23 +0800 Committer: H. Peter Anvin CommitDate: Fri, 20 Jul 2012 15:01:48 -0700 x86/tlb: Fix build warning

Re: [PATCH] Shorten constant names for EFI variable attributes

On 07/20/2012 04:10 PM, H. Peter Anvin wrote: On 07/20/2012 03:08 PM, Khalid Aziz wrote: Replace very long constants for EFI variable attributes with shorter and more convenient names. Also create an alias for the current longer names so as to not break compatibility with current API since

Re: [PATCH v4 24/25] memcg/slub: shrink dead caches

On 07/06/2012 12:16 PM, Christoph Lameter wrote: > On Mon, 18 Jun 2012, Glauber Costa wrote: > >> In the slub allocator, when the last object of a page goes away, we >> don't necessarily free it - there is not necessarily a test for empty >> page in any slab_free path. > > This is the same btw

Re: [PATCH] Shorten constant names for EFI variable attributes

On 07/20/2012 03:08 PM, Khalid Aziz wrote: Replace very long constants for EFI variable attributes with shorter and more convenient names. Also create an alias for the current longer names so as to not break compatibility with current API since these constants are used by userspace programs.

[PATCH] Shorten constant names for EFI variable attributes

Replace very long constants for EFI variable attributes with shorter and more convenient names. Also create an alias for the current longer names so as to not break compatibility with current API since these constants are used by userspace programs. This patch depends on patch

[PATCH] [RFC] [SCSI] mpt fusion: add support for 0x1000/0x0055

The device identifies itself as 0d:05.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01) Subsystem: NEC Corporation SAS1068 and seems to be functionally compatible with 0x0054 PID. The request for support of this device has been raised on mailinglists

[PATCH 13/13] UAPI: Plumb the UAPI Kbuilds into the user header installation and checking

Plumb the UAPI Kbuilds into the user header installation and checking system. As the headers are split the entries will be transferred across from the old Kbuild files to the UAPI Kbuild files. The changes made in this commit are: (1) Exported generated files (of which there are currently four)

[PATCH 12/13] UAPI: x86: Differentiate the generated UAPI and internal headers

Differentiate the generated UAPI and internal headers during generation such that the UAPI headers can be installed elsewhere. A later patch will use this to move the UAPI headers to: arch/x86/include/generated/uapi/asm/ to make them easier to handle. A previous patch added a -I for

[PATCH 11/13] UAPI: Remove the objhdr-y export list

Remove the objhdr-y export list as it is no longer used. genhdr-y should be used instead. Signed-off-by: David Howells --- Documentation/kbuild/makefiles.txt |8 scripts/Makefile.headersinst |7 ++- 2 files changed, 6 insertions(+), 9 deletions(-) diff --git

Re: [PATCH 1/9] workqueue: perform cpu down operations from low priority cpu_notifier()

Hello, Paul. On Fri, Jul 20, 2012 at 02:52:07PM -0700, Paul E. McKenney wrote: > > Fix it by using different priorities for up and down notifiers - high > > priority for up operations and low priority for down operations. > > Cool!!! > > This certainly provides another data point in favor of

[PATCH 10/13] UAPI: Move linux/version.h

Move include/linux/version.h to the include/generated/ header directory. A later patch will move it to include/uapi/generated/. This allows us to get rid of the objhdr-y list. Signed-off-by: David Howells --- Makefile | 13 +++-- include/linux/Kbuild |2 +- 2 files

[PATCH 09/13] UAPI: Set up uapi/asm/Kbuild.asm

Set up uapi/asm/Kbuild.asm. This requires the mandatory headers to be dynamically detected. The same goes for include/asm/Kbuild.asm. The problem is that the header files will be split or moved one at a time, but each header file in Kbuild.asm's list applies to all arch headers of that name

[PATCH 08/13] UAPI: x86: Fix insn_sanity build failure after UAPI split

Fix a build failure in the x86 insn_sanity program after the UAPI split. The problem is that insn_sanity.c #includes arch/x86/lib/insn.c - which uses the kernel string header. This leads to conflicts for various definitions against the /usr/include/ headers. linux/string.h can be replaced with

[PATCH 07/13] UAPI: x86: Fix the test_get_len tool

Fix the x86 test_get_len tool to have the right include paths in the right order (it includes a non-exported kernel header directly), otherwise errors like the following occur: /data/fs/linux-2.6-hdr/include/linux/types.h:18:26: error: conflicting types for 'fd_set'

[PATCH 06/13] UAPI: (Scripted) Set up UAPI Kbuild files

Set up empty UAPI Kbuild files to be populated by the header splitter. Signed-off-by: David Howells --- arch/alpha/include/uapi/asm/Kbuild |3 +++ arch/arm/include/uapi/asm/Kbuild|3 +++ arch/avr32/include/uapi/asm/Kbuild |3 +++

[PATCH 05/13] UAPI: Partition the header include path sets and add uapi/ header directories

Partition the header include path flags into two sets, one for kernelspace builds and one for userspace builds. Add the following directories to build after the ordinary include directories so that #include will pick up the UAPI header directly if the kernel header has been moved there. The

[PATCH 02/13] UAPI: (Scripted) Remove redundant DRM UAPI header #inclusions from drivers/gpu/.

Remove redundant DRM UAPI header #inclusions from drivers/gpu/. Remove redundant #inclusions of core DRM UAPI headers (drm.h, drm_mode.h and drm_sarea.h). They are now #included via drmP.h and drm_crtc.h via a preceding patch. Without this patch and the patch to make include the UAPI headers

[PATCH 00/13] UAPI header file split

Here's the second installment of patches from step 1 of my plan below to clean up the kernel header files and sort out the inclusion recursion problems. Note that these patches will need regenerating if the header files they alter change before they're applied. However, the disintegration is

[PATCH 01/13] UAPI: Refer to the DRM UAPI headers with <...> and from certain headers only

Only refer to the DRM UAPI headers (drm.h, drm_mode.h and drm_sarea.h) from within drmP.h and drm_crtc.h, and use #include <...> to refer to them so that when the UAPI split happens they can still be accessed. Signed-off-by: David Howells Acked-by: Dave Airlie --- include/drm/drmP.h |

[tip:x86/cpufeature] x86, cpufeature: Add the RDSEED and ADX features

Commit-ID: 30d5c4546a7dae29a1aa76abdb69a78bb00136be Gitweb: http://git.kernel.org/tip/30d5c4546a7dae29a1aa76abdb69a78bb00136be Author: H. Peter Anvin AuthorDate: Fri, 20 Jul 2012 13:35:06 -0700 Committer: H. Peter Anvin CommitDate: Fri, 20 Jul 2012 13:36:41 -0700 x86, cpufeature: Add

Re: [PATCH 1/9] workqueue: perform cpu down operations from low priority cpu_notifier()

On Tue, Jul 17, 2012 at 10:12:21AM -0700, Tejun Heo wrote: > Currently, all workqueue cpu hotplug operations run off > CPU_PRI_WORKQUEUE which is higher than normal notifiers. This is to > ensure that workqueue is up and running while bringing up a CPU before > other notifiers try to use

[PATCH] forcedeth: spin_unlock_irq in interrupt handler fix

The replacement of spin_lock_irq/spin_unlock_irq pair in interrupt handler by spin_lock_irqsave/spin_lock_irqrestore pair. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Denis Efremov --- drivers/net/ethernet/nvidia/forcedeth.c |4 ++-- 1 files changed, 2

[PATCH RFT RESEND] net: Fix Neptune ethernet driver to check dma mapping error

Fix Neptune ethernet driver to check dma mapping error after map_page() interface returns. Signed-off-by: Shuah Khan --- drivers/net/ethernet/sun/niu.c |4 1 file changed, 4 insertions(+) diff --git a/drivers/net/ethernet/sun/niu.c b/drivers/net/ethernet/sun/niu.c index

Re: [PATCH RFT] net: Fix Neptune ethernet driver to check dma mapping error

On Fri, 2012-07-20 at 14:30 -0700, David Miller wrote: > From: Shuah Khan > Date: Fri, 20 Jul 2012 15:27:59 -0600 > > > Request for testing, since I don't have the hardware to test. > > This is not how you post a patch. > > >

Re: [patch] tty: handle NULL parameters in free_tty_struct()

On 07/20/2012 11:48 AM, Alan Cox wrote: > On Fri, 20 Jul 2012 10:06:34 +0300 > Dan Carpenter wrote: > >> We sometimes pass NULL pointers to free_tty_struct(). One example where >> it can happen is in the error handling code in pty_common_install(). >> >> Signed-off-by: Dan Carpenter > >

Re: [PATCH RFT] net: Fix Neptune ethernet driver to check dma mapping error

From: Shuah Khan Date: Fri, 20 Jul 2012 15:27:59 -0600 > Request for testing, since I don't have the hardware to test. This is not how you post a patch. > When you put those "---..." there, GIT is going to eliminate

[PATCH RFT] net: Fix Neptune ethernet driver to check dma mapping error

Request for testing, since I don't have the hardware to test. Fix Neptune ethernet driver to check dma mapping error after map_page() interface returns. Signed-off-by: Shuah Khan Cc: --- drivers/net/ethernet/sun/niu.c |

Re: [PATCH][Trivial][resend] Documentation: Add newline at end-of-file to files lacking one

On Fri, 20 Jul 2012, Jesper Juhl wrote: > This patch simply adds a newline character at end-of-file to those > files in Documentation/ that currently lack one. > > This is done for a few different reasons: > > A) It's rather annoying when you do "cat some_file.txt" that your >prompt/cursor

[PATCH -next] m68k/apollo: Rename "timer" to "apollo_timer"

In file included from include/linux/kgdb.h:17, from include/linux/fb.h:8, from drivers/video/dnfb.c:15: include/linux/serial_8250.h:71: error: expected identifier or ‘(’ before numeric constant include/linux/serial_8250.h:72: error: expected ‘;’ before ‘struct’

Re: linux-next: build failure after merge of the tty tree

Hi Alan, On Fri, Jul 20, 2012 at 10:55 PM, Alan Cox wrote: >> Today's build failed because there's a new user in the MIPS tree: >> arch/mips/cavium-octeon/serial.c >> >> http://kisskb.ellerman.id.au/kisskb/buildresult/6739341/ > > The version in the tree I have registers a platform device rather

Re: [PATCH] gpio: samsung: Fix off-by-one bug in gpio addresses

Acked-by: Doug Anderson --- On Fri, Jul 20, 2012 at 1:58 PM, Sean Paul wrote: > > Move gpc4 to the end of the automatically processed gpio controllers so > we don't taint the automatic offset calculation. > > This bug caused all controllers coming after gpc4 to map to the > incorrect address.

Re: oops in kernel ( 3.4.x -> 3.5rc )

On Fri, Jul 20, 2012 at 10:52:40PM +0200, nicolas prochazka wrote: > Hello > the problem is occured with : > - linux kernel 3.4.5i do not test with 3.4.0 / 1 / 2 / 3 / 4, > but i can if you want > - linux kernel 3.5rc6 rc7 / do not test with other rc. > > the problem is not occured with

Re: [PATCH] dmi: Feed DMI table to /dev/random driver

On Fri, 2012-07-20 at 13:15 -0700, Tony Luck wrote: > Send the entire DMI (SMBIOS) table to the /dev/random driver to > help seed its pools. > > Signed-off-by: Tony Luck > --- > > This looks a useful addition to your /dev/random series. There are > lots of platform specific goodies in this

[PATCH] gpio: samsung: Fix off-by-one bug in gpio addresses

Move gpc4 to the end of the automatically processed gpio controllers so we don't taint the automatic offset calculation. This bug caused all controllers coming after gpc4 to map to the incorrect address. The result is < 0 0 0 0> would actually map to GPIO 0 in gpd0. Signed-off-by: Sean Paul ---

Re: [PATCH 0/3] dyndbg: dev_dbg bugfix + 2 trivials

On Fri, Jul 20, 2012 at 04:38:58PM -0400, Jason Baron wrote: > On Thu, Jul 19, 2012 at 01:46:19PM -0600, Jim Cromie wrote: > > 3 patches here, 1st is bugfix, others are trivial. > > > > 1- fix __dev_printk, which broke dev_dbg() prefix under > > CONFIG_DYNAMIC_DEBUG. > > > > Patch looks good,

Re: [PATCH RESEND 5/5] vhost-blk: Add vhost-blk support

"Michael S. Tsirkin" writes: > On Thu, Jul 19, 2012 at 08:05:42AM -0500, Anthony Liguori wrote: >> Of course, the million dollar question is why would using AIO in the >> kernel be faster than using AIO in userspace? > > Actually for me a more important question is how does it compare > with

Re: oops in kernel ( 3.4.x -> 3.5rc )

Hello the problem is occured with : - linux kernel 3.4.5i do not test with 3.4.0 / 1 / 2 / 3 / 4, but i can if you want - linux kernel 3.5rc6 rc7 / do not test with other rc. the problem is not occured with : linux kernel 3.3.4 / 3.3.8 These servers are used for : - starting a lot of

  1   2   3   4   5   6   7   8   9   10   >