From: Namhyung Kim
Currently the symbol structure is allocated with symbol_conf.priv_size
to carry sideband information like annotation, map browser on TUI and
sort-by-name tree node. So retrieving these information from symbol
needs to care about the details of such placement.
However the anno
From: Wang Nan
Perf tool fails to unwind user stack if the event raises in a shared
object. This patch improves tests/dwarf-unwind.c to demonstrate the
problem by utilizing commonly used glibc function "bsearch". If perf is
not statically linked, the testcase will try to unwind a mixed call
trace
From: Arnaldo Carvalho de Melo
We need to use lib/hweight.c for that, just like we do for lib/rbtree.c,
so tools need to link hweight.o. For now do it directly, but we need to
have a tools/lib/lk.a or .so that collects these goodies...
Reported-by: Jan Beulich
Cc: Adrian Hunter
Cc: Borislav Pe
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 33636732dcd7cc738a5913bb730d663c6b03c8fb:
perf/x86/intel: Fix bug for "cycles:p" and "cycles:pp" on SLM (2015-01-16
09:06:59 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/
From: Namhyung Kim
When build with 'make ARCH=x86' and dwarf unwind is on, there is a
compiling error:
CC /home/wn/perf/arch/x86/util/unwind-libdw.o
CC /home/wn/perf/arch/x86/tests/regs_load.o
arch/x86/tests/regs_load.S: Assembler messages:
arch/x86/tests/regs_load.S:65: Erro
From: Namhyung Kim
When it failed to write probe commands to the probe_event file in
debugfs, it needs to propagate the error code properly. Current code
blindly uses the return value of the write(2) so it always uses
-1 (-EPERM) and it might confuse users.
Signed-off-by: Namhyung Kim
Acked-by
On 01/16/2015 04:16 PM, Jeff Layton wrote:
> On Fri, 16 Jan 2015 13:53:04 -0500
> Jeff Layton wrote:
>
>> On Fri, 16 Jan 2015 13:10:46 -0500
>> Sasha Levin wrote:
>>
>>> On 01/16/2015 09:40 AM, Jeff Layton wrote:
On Fri, 16 Jan 2015 09:31:23 -0500
Sasha Levin wrote:
> On 01/1
On Fri, 16 Jan 2015 13:53:04 -0500
Jeff Layton wrote:
> On Fri, 16 Jan 2015 13:10:46 -0500
> Sasha Levin wrote:
>
> > On 01/16/2015 09:40 AM, Jeff Layton wrote:
> > > On Fri, 16 Jan 2015 09:31:23 -0500
> > > Sasha Levin wrote:
> > >
> > >> On 01/15/2015 03:22 PM, Jeff Layton wrote:
> > >>> Ok
Please respond!!!
Hello friend!
I would like to contact you personally for an important proposal that
could of interest to you.
I send this email only to know if this email address is functional.
I have something very important to discuss with you. Contact me for
details by: Email: fernrodyu...@a
On 01/16/2015 04:20 PM, Thomas Gleixner wrote:
> On Fri, 16 Jan 2015, Michael Kerrisk (man-pages) wrote:
>
>> Hello Thomas,
>>
>> On 01/15/2015 11:23 PM, Thomas Gleixner wrote:
>>> On Thu, 15 Jan 2015, Michael Kerrisk (man-pages) wrote:
> [EINVAL] uaddr equal uaddr2. Requeue to same futex.
>>>
On 16 January 2015 at 00:07, Pravin Shelar wrote:
>> @@ -213,13 +223,15 @@ struct flow_stats {
>>
>> struct sw_flow {
>> struct rcu_head rcu;
>> - struct hlist_node hash_node[2];
>> - u32 hash;
>> + struct {
>> + struct hlist_node node[2];
>> +
Em Thu, Jan 15, 2015 at 08:48:20AM +0900, Namhyung Kim escreveu:
> When a dso contains multiple symbols which have same name, current
> dso__find_symbol_by_name() only finds an one of them and there's no way
> to get the all symbols without going through the rbtree.
>
> So add the new 'from' argum
On Fri, Jan 16 2015, Andrew Morton wrote:
> On Fri, 16 Jan 2015 11:23:57 -0500 Johannes Weiner wrote:
>
>> Hi Rasmus,
>>
>> I have trouble booting my test machine with this patch in -mm:
>>
>> commit bb2e066c6943e62e9650bb129f416dacf138f8b1
>> Author: Rasmus Villemoes
>> Date: Wed Jan 14 01
On Fri, Jan 16, 2015 at 01:05:22PM +0100, Robert Rosengren wrote:
> The default sample interval may be too slow for certain clients. This
> patch makes it configurable via the platform_data.
>
> Signed-off-by: Robert Rosengren
> Signed-off-by: Johan Adolfsson
Robert,
can you send me the output
On Fri, Jan 16, 2015 at 08:12:28PM +0100, Hans de Goede wrote:
> On 16-01-15 13:37, Mark Brown wrote:
> >>It is probably a good idea to use regulator-boot-on and
> >>then test things this way, and if that works use
> >>regulator-boot-on.
> >No, it's unlikely that boot-on makes sense here - it's t
On Fri, 16 Jan 2015 11:23:57 -0500 Johannes Weiner wrote:
> Hi Rasmus,
>
> I have trouble booting my test machine with this patch in -mm:
>
> commit bb2e066c6943e62e9650bb129f416dacf138f8b1
> Author: Rasmus Villemoes
> Date: Wed Jan 14 01:00:44 2015 +
>
> lib/vsprintf.c: don't try t
The pty_space() computation is broken; the space already consumed
in the tty buffer is not accounted for.
Use tty_buffer_set_limit(), which enforces the limit automatically.
Signed-off-by: Peter Hurley
---
drivers/tty/pty.c | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-
On 15 January 2015 at 05:26, Kaixu Xia wrote:
> This function coresight_is_bit_set() isn't called, so we should
> remove it.
>
> Signed-off-by: Kaixu Xia
> ---
> include/linux/coresight.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/include/linux/coresight.h b/include/linux/coresig
On 15 January 2015 at 02:49, Kaixu Xia wrote:
> The right debug AMBA bus name should be APB(Advanced Peripheral Bus),
> so just fix it.
>
> Signed-off-by: Kaixu Xia
> ---
> Documentation/trace/coresight.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentatio
On 15 January 2015 at 00:54, Kaixu Xia wrote:
> There are some extra spaces, so just remove them from these lines.
>
> Signed-off-by: Kaixu Xia
> ---
> drivers/coresight/coresight-etb10.c | 2 +-
> drivers/coresight/coresight.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
On 1/16/2015 1:41 PM, Vick, Matthew wrote:
On 1/16/15, 10:59 AM, "Xander Huff" wrote:
From: Jeff Westfahl
The TXPBSIZE register of the i210 resets to its default value only
at power-on. It doesn't reset if you reboot the system, only if you
pull power. If something (another driver, another O
The tty driver will be mistakenly throttled if a line termination
has not been received, and the line exceeds 3967 chars. Thus, it is
possible for the driver to stop sending when it has not yet sent
the newline. This does not apply to the pty driver.
Don't throttle until at least one line terminat
Greg,
Here's the unordered access fix blown up to a series :(
The first patch removes receive_room() from the non-producer code
paths; this avoids the complication of read_head access from the
consumer-side. Exclusive-use paths (where the termios_rwsem is write-locked,
such as n_tty_set_termios()
The adjustments performed by receive_room() are to ensure a line
termination can always be written to the read buffer. However,
these adjustments are irrelevant to the throttle threshold (because
the threshold < buffer limit).
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 2 +-
1 file ch
In canon mode, the read buffer head will advance over the buffer tail
if the input > 4095 bytes without receiving a line termination char.
Discard additional input until a line termination is received.
Before evaluating for overflow, the 'room' value is normalized for
I_PARMRK and 1 byte is reserv
Add commit_head buffer index, which the producer-side publishes
after input processing in non-canon mode. This ensures the consumer-side
observes correctly-ordered writes in non-canonical mode (ie., the buffer
data is written before the buffer index is advanced). Fix consumer-side
uses of read_cnt(
The input worker never reschedules itself; it only processes input until
either there is no more input or the read buffer is full. So the reader
is responsible for restarting the input worker only if the read buffer
was previously full (no_room == 1) _and_ space is now available to process
more inp
If PARMRK is enabled, the available read buffer space computation is
overly-pessimistic, which results in severely throttled i/o, even
in the absence of parity errors. For example, if the 4k read buffer
contains 1k processed data, the input worker will compute available
space of 333 bytes, despite
On 01/16/2015 08:26 AM, Aneesh Kumar K.V wrote:
> This make sure that we try to allocate hugepages from local node if
> allowed by mempolicy. If we can't, we fallback to small page allocation
> based on mempolicy. This is based on the observation that allocating pages
> on local node is more benefi
On Fri, Jan 16, 2015 at 8:17 AM, Russell King - ARM Linux
wrote:
> On Sat, Jan 17, 2015 at 01:08:11AM +0900, Roman Peniaev wrote:
>> On Sat, Jan 17, 2015 at 12:59 AM, Russell King - ARM Linux
>> wrote:
>> > On Sat, Jan 17, 2015 at 12:57:02AM +0900, Roman Peniaev wrote:
>> >> On Fri, Jan 16, 2015
On 16/01/15 19:37, William Cohen wrote:
On 01/16/2015 01:29 PM, Zoltan Kiss wrote:
On 16/01/15 15:38, William Cohen wrote:
On 01/16/2015 09:01 AM, Zoltan Kiss wrote:
Hi,
I'm using OProfile to check some suspicious behaviour of dpdk-pktgen,
and I can see something which troubles me. Either
Hello,
On Fri, Jan 16, 2015 at 11:24:09AM -0800, Ray Jui wrote:
> >> + i2c0: i2c@18008000 {
> >> + compatible = "brcm,iproc-i2c";
> > in patch 2 you wrote the driver is for a family of SoCs, right? Then I'd
> > make this:
> >
> > compatible = "brcm,$mysoc-iproc-i2c", "brcm,iproc-i2c
On Fri, Jan 16, 2015 at 08:13:36PM +0100, Hans de Goede wrote:
> On 16-01-15 16:34, Mark Brown wrote:
> >>As pointed by Hans my concern here was be sure that during boot the disk
> >>are not power off. In this case which property would be accurate?
> >None, the core won't do anything with the reg
On 1/16/15, 10:59 AM, "Xander Huff" wrote:
>From: Jeff Westfahl
>
>The TXPBSIZE register of the i210 resets to its default value only
>at power-on. It doesn't reset if you reboot the system, only if you
>pull power. If something (another driver, another OS, etc.) modifies
>this register from its
Hi,
Another fun fact I forgot to mention: if I profile only this thread, and
then run opreport with cpu filtering, it only shows results on the right
cpu. So the wrong accounting only happens when I do system wide
profiling. But not just with this thread and function, other functions
appear a
On 01/16/2015 01:29 PM, Zoltan Kiss wrote:
>
>
> On 16/01/15 15:38, William Cohen wrote:
>> On 01/16/2015 09:01 AM, Zoltan Kiss wrote:
>>> Hi,
>>>
>>> I'm using OProfile to check some suspicious behaviour of dpdk-pktgen,
>>> and I can see something which troubles me. Either the scheduler lies
>>>
On 01/09/15 09:25, Harry Edmon wrote:
I have a system with a Supermicro X10DRL-i motherboard and dual Xeon E5-2620
processors. The system runs fine under 3.17.7, but crashes under 3.18.1 and
3.18.2. Below is the crash dump and kernel configuration file. Does anyone
have any suggestions sh
>From 29187a9eeaf362d8422e62e17a22a6e115277a49 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 16 Jan 2015 14:21:16 -0500
A worker_pool's forward progress is guaranteed by the fact that the
last idle worker assumes the manager role to create more workers and
summon the rescuers if creating wo
On 01/14/15 04:30, Pratyush Anand wrote:
Hi Dave,
On Sun, Jan 11, 2015 at 9:33 AM, David Long wrote:
From: Sandeepa Prabhu
Add support for basic kernel probes(kprobes) and jump probes
(jprobes) for ARM64.
Kprobes will utilize software breakpoint and single step debug
exceptions supported on
From: Michael Kerrisk
This patch fixes two separate buglets in calls to futex_lock_pi():
* Eliminate unused 'detect' argument
* Change unused 'timeout' argument of FUTEX_TRYLOCK_PI to NULL
The 'detect' argument of futex_lock_pi() seems never to have been
used (when it was included with the
From: Michael Kerrisk
FUTEX_CMP_REQUEUE_PI was misnamed in two different ways:
FUTEX_REQUEUE_CMP_PI and FUTEX_REQUEUE_PI. The existence of two
different misnamings leaves the reader wondering if we are talking
about two different operations. Furthermore, the misnamings mean
that grepping the sour
Hello Thomas,
While working on revisions to the futex(2) man page, I noticed
a couple of source files that could be improved. In one Doc file,
important constants are misnamed, so that grepping won't find
useful information. And in the futex.c code, the argument handling
in futex_lock_pi() is a li
On 1/15/2015 12:44 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Jan 14, 2015 at 02:23:33PM -0800, Ray Jui wrote:
>> Add I2C device nodes and its properties in bcm-cygnus.dtsi but keep
>> them disabled there. Individual I2C devices can be enabled in board
>> specific dts file when I2C slave d
From: Daniel Mack
This patch adds the header file which describes the low-level
transport protocol used by various ioctls. The header file is located
in include/uapi/linux/ as it is shared between kernel and userspace,
and it only contains data structure definitionsi, enums and #defines
for const
From: Daniel Mack
This patch adds code to create and destroy connections, to validate
incoming messages and to maintain the queue of messages that are
associated with a connection.
Note that connection and queue have a 1:1 relation, the code is only
split in two parts for cleaner separation and
From: Daniel Mack
kdbusfs is a filesystem that will expose a fresh kdbus domain context
each time it is mounted. Per mount point, there will be a 'control'
node, which can be used to create buses. fs.c contains the
implementation of that pseudo-fs. Exported inodes of 'file' type have
their i_fop
From: Daniel Mack
Add the basic driver structure.
handle.c is the main ioctl command dispatcher that calls into other parts
of the driver.
main.c contains the code that creates the initial domain at startup, and
util.c has utility functions such as item iterators that are shared with
other file
On Fri, 16 Jan 2015, Michal Hocko wrote:
> On Fri 16-01-15 16:49:22, Michal Hocko wrote:
> [...]
> > Why cannot we simply update the global counters from vmstat_shepherd
> > directly?
>
> OK, I should have checked the updating paths... This would be racy, so
> update from remote is not an option w
From: Daniel Mack
A connection chooses which metadata it wants to have attached to each
message it receives with kdbus_cmd_hello.attach_flags. The metadata
will be attached as items to the messages. All metadata refers to
information about the sending task at sending time, unless otherwise
stated
From: Daniel Mack
A pool for data received from the kernel is installed for every
connection of the bus, and it is used to copy data from the kernel to
userspace clients, for messages and other information.
It is accessed when one of the following ioctls is issued:
* KDBUS_CMD_MSG_RECV, to re
From: Daniel Mack
Add the logic to handle the following entities:
Domain:
A domain is an unamed object containing a number of buses. A
domain is automatically created when an instance of kdbusfs
is mounted, and destroyed when it is unmounted.
Every domain offers its own "control" device
From: Daniel Mack
This patch hooks up the build system to actually compile the files
added by previous patches. It also adds an entry to MAINTAINERS to
direct people to Greg KH, David Herrmann, Djalal Harouni and me for
questions and patches.
Signed-off-by: Daniel Mack
Signed-off-by: David Herr
From: Daniel Mack
This patch adds code for matches and notifications.
Notifications are broadcast messages generated by the kernel, which
notify subscribes when connections are created or destroyed, when
well-known-names have been claimed, released or changed ownership,
or when reply messages ha
From: Daniel Mack
This patch adds the name registry implementation.
Each bus instantiates a name registry to resolve well-known names
into unique connection IDs for message delivery. The registry will
be queried when a message is sent with kdbus_msg.dst_id set to
KDBUS_DST_ID_NAME, or when a reg
From: Daniel Mack
This patch adds the policy database implementation.
A policy databases restrict the possibilities of connections to own,
see and talk to well-known names. It can be associated with a bus
(through a policy holder connection) or a custom endpoint.
By default, buses have an empty
kdbus is a kernel-level IPC implementation that aims for resemblance to
the the protocol layer with the existing userspace D-Bus daemon while
enabling some features that couldn't be implemented before in userspace.
The documentation in the first patch in this series explains the
protocol and the A
From: Daniel Mack
kdbus is a system for low-latency, low-overhead, easy to use
interprocess communication (IPC).
The interface to all functions in this driver is implemented via ioctls
on files exposed through a filesystem called 'kdbusfs'. The default
mount point of kdbusfs is /sys/fs/kdbus. Th
Hi,
On 16-01-15 16:34, Mark Brown wrote:
On Fri, Jan 16, 2015 at 03:27:00PM +0100, Gregory CLEMENT wrote:
On 16/01/2015 13:37, Mark Brown wrote:
regulator-always-on is a bit fuzzy for suspend, if the regulator has
suspend control it'll kick in - it's really about the Linux refcounting
while
Hi,
On 16-01-15 13:37, Mark Brown wrote:
On Fri, Jan 16, 2015 at 11:10:18AM +0100, Hans de Goede wrote:
On 16-01-15 10:27, Gregory CLEMENT wrote:
+ reg_sata0: pwr-sata0 {
+ compatible = "regulator-fixed";
+ regulator-name = "pwr_en_sata0";
+ en
Hi Stuart,
On 15/01/15 20:35, Stuart Yoder wrote:
> On Thu, Jan 8, 2015 at 11:06 AM, Marc Zyngier wrote:
>> As MSI-type features are creeping into non-PCI devices, it is
>> starting to make sense to give our struct device some form of
>> support for this, by allowing a pointer to an MSI irq domai
Jia He,
Your patch is looking better :-)
A few nits though.
On Fri, Jan 16, 2015 at 04:58:12PM +0800, Jia He wrote:
> These functions kportal_memhog_{alloc,free} aren't used outside of
^ Don't indent paragraphs, just use a line between paragraphs.
> this file, so making them static to supp
On Fri, Jan 16, 2015 at 8:57 AM, Alexandre Belloni
wrote:
> Track whether the clocksource is enabled or disabled.
So.. this commit message needs work. Why do we care to track the
clocksource enabled/disabled state?
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-
On Thu, Jan 15, 2015 at 09:22:45PM -, Thomas Gleixner wrote:
> Now that the APIC bringup is consolidated we can move the setup call
> for the percpu clock event device to apic_bsp_setup().
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
--
Regards/Gruss,
Boris.
ECO tip #
On Fri, Jan 16, 2015 at 12:05:24PM +0100, Thomas Gleixner wrote:
> On Fri, 16 Jan 2015, Thomas Gleixner wrote:
> > On Fri, 16 Jan 2015, Jiang Liu wrote:
> > > 5) x86_32, UP, IO_APIC disabled
> > > 5.1) boot: panic with following call stack:
> > > do_ono_initcall()->APIC_init_uniprocessor()->setup_l
On Thu, Jan 15, 2015 at 09:22:44PM -, Thomas Gleixner wrote:
> Extend apic_bsp_setup() so the same code flow can be used for
> APIC_init_uniprocessor().
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
On Thu, Jan 15, 2015 at 09:22:40PM -, Thomas Gleixner wrote:
> We better provide proper functions which implement the required code
> flow in the apic code rather than letting the smpboot code open code
> it. That allows to make more functions static and confines the APIC
> functionality to api
On Thu, Jan 15, 2015 at 09:22:42PM -, Thomas Gleixner wrote:
> The UP related setups for local apic are mangled into smp_sanity_check().
>
> That results in duplicate calls to disable_smp() and makes the code
> hard to follow. Let smp_sanity_check() return dedicated values for the
> various ex
On 01/16/2015 07:53 PM, Vlastimil Babka wrote:
> BTW, I wonder if the whole code couldn't be much simpler by capping
> high_zoneidx
> by ZONE_NORMAL before traversing the zonelist, like this:
>
> int high_zoneidx = min(gfp_zone(gfp_mask), ZONE_NORMAL);
>
> first_zones_zonelist(zonelist, high_zon
On Thu, Jan 15, 2015 at 09:22:32PM -, Thomas Gleixner wrote:
> No point to have the same checks at every call site. Add them to the
> functions, so they can be called unconditionally.
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
--
Regards/Gruss,
Boris.
ECO tip #101:
On Thu, Jan 15, 2015 at 09:22:37PM -, Thomas Gleixner wrote:
> Move the code to a different place so we can make other functions
> inline. Preparatory patch for further cleanups. No change.
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
--
Regards/Gruss,
Boris.
ECO tip
On Thu, Jan 15, 2015 at 09:22:29PM -, Thomas Gleixner wrote:
> No point for a seperate header file.
s/seperate/separate/
>
> Signed-off-by: Thomas Gleixner
> ---
> arch/x86/include/asm/smpboot_hooks.h | 68
> ---
> arch/x86/kernel/smpboot.c|
On Thu, Jan 15, 2015 at 09:22:34PM -, Thomas Gleixner wrote:
> We have proper stubs for the IOAPIC=n case and the setup/enable
> function have the required checks inside now. Remove the ifdeffery and
> the copy&pasted conditionals.
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
On Thu, Jan 15, 2015 at 09:22:35PM -, Thomas Gleixner wrote:
> smpboot is very creative with the ways to disable ioapic.
>
> smpboot_clear_io_apic() smpboot_clear_io_apic_irqs() and
> disable_ioapic_support() serve a similar purpose.
>
> smpboot_clear_io_apic_irqs() is the most useless of all
On Thu, Jan 15, 2015 at 09:22:27PM -, Thomas Gleixner wrote:
> Use the state information to simplify the disable logic further.
>
> Signed-off-by: Thomas Gleixner
Acked-by: Borislav Petkov
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe fro
On Thu, Jan 15, 2015 at 09:22:30PM -, Thomas Gleixner wrote:
> To avoid lots of ifdeffery provide proper stubs for setup_IO_APIC(),
> enable_IO_APIC() and setup_ioapic_dest().
>
> Signed-off-by: Thomas Gleixner
Very nice, that ifdeffery was uuugly...
Acked-by: Borislav Petkov
--
Regards/
From: Jeff Westfahl
The TXPBSIZE register of the i210 resets to its default value only
at power-on. It doesn't reset if you reboot the system, only if you
pull power. If something (another driver, another OS, etc.) modifies
this register from its default value, the igb driver doesn't function
cor
On Thu, Jan 15, 2015 at 09:22:24PM -, Thomas Gleixner wrote:
> There is no point in postponing the hardware disablement of x2apic. It
> can be disabled right away in the nox2apic setup function.
>
> Disable it right away and set the state to DISABLED . This allows to
> remove all the nox2apic
On Thu, Jan 15, 2015 at 09:22:26PM -, Thomas Gleixner wrote:
> enable_x2apic() is a convoluted unreadable mess because it is used for
> both enablement in early boot and for setup in cpu_init().
>
> Split the code into x2apic_enable() for enablement and x2apic_setup()
> for setup of (secondary
Hi,
On Fri, Jan 16, 2015 at 12:19:50PM +0100, Krzysztof Kozlowski wrote:
> Add myself as supporter for Maxim 77686 PMIC and Maxim 14577/77693 MUIC
> drivers:
> - mfd (all of them),
> - extcon (extcon-max14577, extcon-max77693)
> - power (max14577_charger.c, 77693 on LKML [1]),
> - regulator (a
On 01/16/2015 12:00 PM, Chris Mason wrote:
> On Fri, Jan 16, 2015 at 11:56 AM, Peter Hurley
> wrote:
>> Peter & Kent,
>>
>> What's the plan here?
>
> I'm cleaning up my patch slightly and resubmitting.
Awesome. Will you copy me on it, please?
Regards,
Peter Hurley
--
To unsubscribe from this
On Thu, Jan 15, 2015 at 09:22:22PM -, Thomas Gleixner wrote:
> Having 3 different variables to track the state is just silly and
> error prone. Add a proper state tracking variable which covers the
> three possible states: ON/OFF/DISABLED.
>
> We cannot use x2apic_mode for this as this would r
On Fri, Jan 16, 2015 at 7:02 AM, Steven Rostedt wrote:
> On Thu, 15 Jan 2015 20:16:01 -0800
> Alexei Starovoitov wrote:
>
>> Hi Ingo, Steven,
>>
>> This patch set is based on tip/master.
>
> Note, the tracing code isn't maintained in tip/master, but perf code is.
I know. I can rebase against lin
On Fri, 16 Jan 2015, Peter Zijlstra wrote:
> On Fri, Jan 16, 2015 at 11:46:44AM +0100, Peter Zijlstra wrote:
> > Its a bandaid at best :/ The problem is (again) that we changes
> > event->ctx without any kind of serialization.
> >
> > The issue came up before:
> >
> > https://lkml.org/lkml/2014
On 01/16/2015 08:07 AM, Michael S. Tsirkin wrote:
> On Thu, Jan 15, 2015 at 02:49:20PM -0800, Andrew Morton wrote:
>> On Fri, 16 Jan 2015 00:18:12 +0200 "Michael S. Tsirkin"
>> wrote:
>>
>> > for_each_zone_zonelist_nodemask wants an enum zone_type
>> > argument, but is passed gfp_t:
>> >
>> > m
On Fri, 16 Jan 2015 13:10:46 -0500
Sasha Levin wrote:
> On 01/16/2015 09:40 AM, Jeff Layton wrote:
> > On Fri, 16 Jan 2015 09:31:23 -0500
> > Sasha Levin wrote:
> >
> >> On 01/15/2015 03:22 PM, Jeff Layton wrote:
> >>> Ok, I tried to reproduce it with that and several variations but it
> >>> st
There are no drivers in the kernel that implement the uio_info mmap
method so there is no point in keeping it.
Further keeping the mmap method would necessitate wrapping all of the
methods in vm_operations_struct to successfully implement support for
hotunplugable hardware, and it I have yet to fi
With this change it is possible to remove a module that implements
a uio device, or to remove the underlying hardware device of a uio
device withot crashing the kernel, or causing user space more problems
than just an I/O error.
The implicit module parameter that was passed by uio_register_device
The problem of how to remove open files due to module unloading or
device hotunplugging keeps coming up. We have multiple implementations
of roughly the same logic in proc, sysctl, sysfs, tun and now I am
working on yet another one for uio. It is time to start working on a
generic implementation.
Embed struct device into struct uio_device, and use
the refcounting and the release method of struct device
to control struct uio_device.
This allows device_create and device_destroy to be replaced
with the more standard device_register and device_unregister,
and allows the struct device reference
I'm re-submitting this patch originally authored by Eric W. Biederman.
See: https://lkml.org/lkml/2010/9/20/21
Implement the ability to hot-unplug a uio device while file handles
are still open, without crashing.
The "locking" for hotunplug support is implemented in
a generic library, that shou
The following changes since commit b7392d2247cfe6771f95d256374f1a8e6a6f48d6:
Linux 3.19-rc2 (2014-12-28 16:49:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-3.19-rc5
for you to fetch changes up to 7b7c549
I'm announcing the release of the 3.14.29 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.18.3 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 69b3cac4749d..5d8675615e59 100644
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramoops.txt
@@ -14,11 +14,19 @@ survive after a restart.
1. Ramoops concepts
-Ramoops uses a predefined memory area to store the dump.
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 69b3cac4749d..5d8675615e59 100644
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramoops.txt
@@ -14,11 +14,19 @@ survive after a restart.
1. Ramoops concepts
-Ramoops uses a predefined memory area to store the dump.
I'm announcing the release of the 3.10.65 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web browser:
On Fri, Jan 16, 2015 at 06:36:14PM +0100, Paul Osmialowski wrote:
> On Fri, 16 Jan 2015, Mark Brown wrote:
> >I don't know what this means, sorry. I'm also very worried about the
> >fact that this is being discussed purely in terms of I2C - why would
> >this not affect other buses?
> I tried to
2015-01-16 16:07+0800, Li Kaihang:
> > GuestOS is running and handling some interrupt with RFLAGS.IF = 0 while a
> > external interrupt coming,
> > then can lead to a vm exit,in this case,we must avoid inject this external
> > interrupt or it will generate
> > a processor hardware exception causi
The following changes since commit b7392d2247cfe6771f95d256374f1a8e6a6f48d6:
Linux 3.19-rc2 (2014-12-28 16:49:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.19-rc5
for you to fetch changes up to 723
The following changes since commit b7392d2247cfe6771f95d256374f1a8e6a6f48d6:
Linux 3.19-rc2 (2014-12-28 16:49:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/
tags/tty-3.19-rc5
for you to fetch changes up to 31ec77aca72ee5920ed
101 - 200 of 592 matches
Mail list logo
