Hi Quentin,
it looks like there is another failure in linux-next, this time with
sparc64:allmodconfig:
WARNING: arch/sparc/kernel/built-in.o(__ex_table+0x3b4): Section mismatch in
reference from the (unknown reference) (unknown) to the variable :__retl_efault
/bin/sh: line 1: 22844 Floating
Hi all,
I see the following build failure when compiling sparc64:allmodconfig
in the upstream kernel (v4.0-7820-g04b7fe6a4a23).
arch/sparc/kernel/pci_sun4v.o:(.discard+0x1): multiple definition of
`__pcpu_unique_iommu_pool_hash'
arch/sparc/kernel/iommu.o:(.discard+0x0): first defined here
On Apr 17 2015, Mike Galbraith wrote:
> On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
>>
>> Is there anything I can do to help debug this issue?
>
> You could try to bisect it, but judging from the problem description,
> that could be more like a career than a troubleshooting session.
On Fri, 2015-04-17 at 21:13 -0700, Nikolaus Rath wrote:
> On Apr 17 2015, Mike Galbraith wrote:
> > On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
> > >
> > > Is there anything I can do to help debug this issue?
> >
> > You could try to bisect it, but judging from the problem
> >
On Fri, Apr 17, 2015 at 6:35 PM, Dan Williams wrote:
> ACPI 6.0 formalizes e820-type-7 and efi-type-14 as persistent memory.
> Mark it "reserved" and allow it to be claimed by a persistent memory
> device driver.
>
> This definition is in addition to the Linux kernel's existing type-12
>
Hi Dongsu,
On Fri, Apr 17, 2015 at 5:41 AM, Dongsu Park
wrote:
> Hi,
>
> there's a critical bug regarding CPU hotplug, blk-mq, and scsi-mq.
> Every time when a CPU is offlined, some arbitrary range of kernel memory
> seems to get corrupted. Then after a while, kernel panics at random places
>
On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
>
> Is there anything I can do to help debug this issue?
You could try to bisect it, but judging from the problem description,
that could be more like a career than a troubleshooting session.
-Mike
--
To unsubscribe from this
Let's zero-extend hardware id number when forming firmware file name,
to avoid kernel requesting firmware like "elants_i2c_ 0.bin", which
is quite unexpected.
Signed-off-by: Dmitry Torokhov
---
drivers/input/touchscreen/elants_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 03/19/2015 08:57 PM, Mike Galbraith wrote:
> (+CC)
>
> On Thu, 2015-03-19 at 20:21 -0700, Nikolaus Rath wrote:
>> On Mar 13 2015, Nikolaus Rath wrote:
>>> Hello,
>>>
>>> In about one out of 10 resumes from hibernation, my system resets after
>>> the hibernation image has been loaded. I am
On Mon, Mar 23, 2015 at 01:37:38PM +1100, NeilBrown wrote:
> lustre's ->follow_link() uses a lot of stack space and so
> need to limit symlink recursion based on stack size.
>
> It currently tests current->link_count, but that will soon
> become private to fs/namei.c.
> So instead base on actual
On Sat, Apr 18, 2015 at 04:04:14AM +0200, Stephan Mueller wrote:
>
> However, the only serious solution I can offer to not block is to use my
> Jitter RNG which delivers entropy in (almost all) use cases. See [1]. The
> code
> is relatively small and does not have any dependencies. In this
In up_read()/up_write(), rwsem_wake() will be called whenever it
detects that some writers/readers are waiting. The rwsem_wake()
function will take the wait_lock and call __rwsem_do_wake() to do
the real wakeup. This can be a problem especially for up_read()
where many readers can potentially
On 04/17/2015 05:51 PM, Dave Chinner wrote:
On Fri, Apr 17, 2015 at 05:11:40PM -0600, Jens Axboe wrote:
On 04/17/2015 05:06 PM, Dave Chinner wrote:
On Thu, Apr 16, 2015 at 11:20:45PM -0700, Ming Lin wrote:
On Sat, Apr 11, 2015 at 4:59 AM, Dave Chinner wrote:
On Fri, Apr 10, 2015 at
On Fri, Apr 17, 2015 at 06:38:49PM -0400, Mike Snitzer wrote:
>
> There are also some crypto changes that could very easily be the cause
> of your problem (cc'ing Herbert), e.g.:
>
> $ git diff next-20150410^..next-20150413 -- crypto | diffstat
My guess is that you guys need this patch:
commit
1/ Autodetect an NFIT table for the ACPI namespace device with _HID of
"ACPI0012"
2/ Skeleton implementation to register an NFIT bus.
The NFIT provided by ACPI is the primary method by which platforms will
discover NVDIMM resources. However, the intent of the
nfit_bus_descriptor abstraction
A complete label set is a PMEM-label per dimm where all the UUIDs
match and the interleave set cookie matches an active interleave set.
Present a sysfs ABI for manipulation of a PMEM-namespace's 'alt_name',
'uuid', and 'size' attributes. A later patch will make these settings
persistent by
* Implement the device-model infrastructure for loading modules and
attaching drivers to nd devices. This is a simple association of a
nd-device-type number with a driver that has a bitmask of supported
device types. To facilitate userspace bind/unbind operations 'modalias'
and
Basic allocation and parsing of an nfit table. This is infrastructure
for walking the list of "System Physical Address (SPA) Range Tables",
and "Memory device to SPA" to create "region" devices representing
persistent-memory (PMEM) or a dimm block data window set (BLK).
Note, BLK windows may be
On media label format consists of two index blocks followed by an array
of labels. None of these structures are ever updated in place. A
sequence number tracks the current active index and the next one to
write, while labels are written to free slots.
++
||
|
Manually create and register NFITs to describe 2 topologies. Topology1
is an advanced plausible configuration for BLK/PMEM aliased NVDIMMs.
Topology2 is an example configuration for current platforms that only
ship with a persistent address range.
Kernel provider "nfit_test.0" produces an NFIT
From: Vishal Verma
BTT stands for Block Translation Table, and is a way to provide power
fail sector atomicity semantics for block devices that have the ability
to perform byte granularity IO. It relies on the ->rw_bytes() capability
of provided nd namespace devices.
The BTT works as a stacked
On platforms that have firmware support for reading/writing per-dimm
label space, a portion of the dimm may be accessible via an interleave
set PMEM mapping in addition to the dimm's BLK (block-data-window
aperture(s)) interface. A label, stored in a "configuration data
region" on the dimm,
The NFIT region driver is an intermediary driver that translates NFIT
defined "region"s into "namespace" devices that are consumed by
persistent memory block drivers. A "namespace" is a sub-division of a
region.
Support for NVDIMM labels is reserved for a later patch. For now,
publish
A "region" device represents the maximum capacity of a
block-data-window, or an interleaved spa range (direct-access persistent
memory or volatile memory), without regard for aliasing. Aliasing is
resolved by the label data on the dimm to designate which exclusive
interface will access the
Most configuration of the nd-subsystem is done via nd-sysfs. However,
the NFIT specification defines a small set of messages that can be
passed to the subsystem via platform-firmware-defined methods. The
command set (as of the current version of the NFIT-DSM spec) is:
NFIT_CMD_SMART: media
Block devices from an nd bus, in addition to accepting "struct bio"
based requests, also have the capability to perform byte-aligned
accesses. By default only the bio/block interface is used. However, if
another driver can make effective use of the byte-aligned capability it
can claim/disable
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
Cc: Andy Lutomirski
Cc: Boaz Harrosh
Cc: H. Peter Anvin
Cc: Jens Axboe
Cc: Ingo Molnar
Cc: Christoph
After 'uuid', 'size', 'sector_size', and optionally 'alt_name' have been
set to valid values the labels on the dimm can be updated. The
difference with the pmem case is that blk namespaces are limited to one
dimm and can cover discontiguous ranges in dpa space.
Also, after allocating label
After 'uuid', 'size', and optionally 'alt_name' have been set to valid
values the labels on the dimms can be updated.
Write procedure is:
1/ Allocate and write new labels in the "next" index
2/ Free the old labels in the working copy
3/ Write the bitmap and the label space on the dimm
4/ Write
From: Ross Zwisler
Block-device driver for BLK namespaces described by DCR (dimm control
region), BDW (block data window), and IDT (interleave descriptor) NFIT
structures.
The BIOS may choose to interleave multiple dimms into a given SPA
(system physical address) range, so this driver includes
A blk label set describes a namespace comprised of one or more
discontiguous dpa ranges on a single dimm. They may alias with one or
more pmem interleave sets that include the given dimm.
This is the runtime/volatile configuration infrastructure for sysfs
manipulation of 'alt_name', 'uuid',
ACPI 6.0 formalizes e820-type-7 and efi-type-14 as persistent memory.
Mark it "reserved" and allow it to be claimed by a persistent memory
device driver.
This definition is in addition to the Linux kernel's existing type-12
definition that was recently added in support of shipping platforms with
Maintainer information and documenation for drivers/block/nd/
Cc: Andy Lutomirski
Cc: Boaz Harrosh
Cc: H. Peter Anvin
Cc: Jens Axboe
Cc: Ingo Molnar
Cc: Christoph Hellwig
Cc: Neil Brown
Cc: Greg KH
Signed-off-by: Dan Williams
---
Documentation/blockdev/nd.txt | 867
This is the position (device topology) independent method to find all
the NFIT-defined buses in the system. The expectation is that there
will only ever be one "nd" bus discovered via /sys/class/nd/ndctl0.
However, we allow for the possibility of multiple buses and they will
listed in discovery
Register the dimms described in the nfit as devices on a nd_bus, named
"dimmN" where N is a global ida index. The dimm numbering per-bus may
appear contiguous, since we only allow a single nd_bus to be registered
at at a time. However, eventually, dimm-hotplug invalidates this
property and dimms
Since 2010 Intel has included non-volatile memory support on a few
storage-focused platforms with a feature named ADR (Asynchronous DRAM
Refresh). These platforms were mostly targeted at custom applications
and never enjoyed standard discovery mechanisms for platform firmware
to advertise
From: Andi Kleen
Currently we don't reset FPU state on exec. This can be seen as a
(minor) security issue. The bigger issue however is that the
AVX state also does not get reset. So a program that uses SSE
without VZEROUPPER may get a large penalty.
Always set the FPU to the init state at exec
> ... which would give you arbitrary skew, because one counter is
> free-running and the other is not (when scheduling a context in or out we stop
> the PMU)
Everyone just reads the counter and subtracts it from
the last value they've seen.
That's the same how any other shared free running
From: Philippe De Muyter
This is a basic driver for the ultra-low-power Abracon AB x80x series of RTC
chips. It supports in particular, the supersets AB0805 and AB1805.
It allows reading and writing the time, and enables the supercapacitor/
battery charger.
[a...@arndb.de: abx805 depends on
On Fri, Apr 17, 2015 at 08:35:30PM +0800, Boqun Feng wrote:
> Hi Al,
>
> On Sun, Apr 12, 2015 at 02:13:18AM +0100, Al Viro wrote:
> >
> > BTW, looking at the __getname() callers... Lustre one sure as hell looks
> > bogus:
> > char *tmp = __getname();
> >
> > if (!tmp)
> >
A deadlock can be initiated by userspace via ioctl(SNDCTL_SEQ_OUTOFBAND)
on /dev/sequencer with TMR_ECHO midi event.
In this case the control flow is:
sound_ioctl()
-> case SND_DEV_SEQ:
case SND_DEV_SEQ2:
sequencer_ioctl()
-> case SNDCTL_SEQ_OUTOFBAND:
On Fri, Apr 17, 2015 at 05:11:40PM -0600, Jens Axboe wrote:
> On 04/17/2015 05:06 PM, Dave Chinner wrote:
> >On Thu, Apr 16, 2015 at 11:20:45PM -0700, Ming Lin wrote:
> >>On Sat, Apr 11, 2015 at 4:59 AM, Dave Chinner wrote:
> >>>On Fri, Apr 10, 2015 at 04:50:05PM -0700, Ming Lin wrote:
> On
> -Original Message-
> From: Paul E. McKenney [mailto:paul...@linux.vnet.ibm.com]
> Sent: Friday, April 17, 2015 11:41 AM
> To: Jeff Haran
> Cc: Milos Vyletel; Josh Triplett; Steven Rostedt; Mathieu Desnoyers; Lai
> Jiangshan; Jonathan Corbet; open list:READ-COPY UPDATE...; open
>
On Fri, Apr 17, 2015 at 01:38:49PM -0400, Waiman Long wrote:
> Hi Dave,
>
> When I was running the AIM7's disk workload on a 8-socket
> Westmere-EX server with 4.0 kernel, the kernel crash. A set of small
> ramdisks were created (ramdisk_size=271072). Those ramdisks were
> formatted with XFS
On Fri, Apr 17, 2015 at 03:25:28PM -0700, Andy Lutomirski wrote:
> On Fri, Apr 17, 2015 at 3:04 PM, Linus Torvalds
> wrote:
> > On Fri, Apr 17, 2015 at 5:42 PM, Andy Lutomirski
> > wrote:
> >>
> >> Muahaha. The auditors have invaded your system. (I did my little
> >> benchmark with a more
On 04/17/2015 05:06 PM, Dave Chinner wrote:
On Thu, Apr 16, 2015 at 11:20:45PM -0700, Ming Lin wrote:
On Sat, Apr 11, 2015 at 4:59 AM, Dave Chinner wrote:
On Fri, Apr 10, 2015 at 04:50:05PM -0700, Ming Lin wrote:
On Wed, Mar 25, 2015 at 7:26 AM, Jens Axboe wrote:
If
On Thu, Apr 16, 2015 at 11:20:45PM -0700, Ming Lin wrote:
> On Sat, Apr 11, 2015 at 4:59 AM, Dave Chinner wrote:
> > On Fri, Apr 10, 2015 at 04:50:05PM -0700, Ming Lin wrote:
> >> On Wed, Mar 25, 2015 at 7:26 AM, Jens Axboe wrote:
> >> >> If iocb->ki_filp->f_streamid is not set, then it should
On Sat, Apr 18, 2015 at 12:16:48AM +0200, Mateusz Guzik wrote:
> I would say this makes the use of seq counter impossible. Even if we
> decided to fall back to a lock on retry, we cannot know what to do if
> the slot is reserved - it very well could be that something called
> close, and something
On Apr 17, 2015, at 5:31 AM, Jan Kara wrote:
> On Wed 15-04-15 09:15:44, Beata Michalska wrote:
>> Introduce configurable generic interface for file
>> system-wide event notifications to provide file
>> systems with a common way of reporting any potential
>> issues as they emerge.
>>
>> The
On Fri, Apr 17 2015 at 4:11pm -0400,
Murilo Opsfelder Araújo wrote:
> Hello, everyone.
>
> Right after I enter my passphrase to unlock my cryptsetup partition,
> it displays the following error and asks for cryptsetup password again
> (it got stuck on this loop).
>
> This issue was introduced
On Apr 17, 2015, at 11:37 AM, John Spray wrote:
> On 17/04/2015 17:22, Jan Kara wrote:
>> On Fri 17-04-15 17:08:10, John Spray wrote:
>>> On 17/04/2015 16:43, Jan Kara wrote:
>>> In that case I'm confused -- why would ENOSPC be an appropriate use
>>> of this interface if the mount being entirely
On 17 April 2015 at 15:28, Andy Lutomirski wrote:
> On Fri, Apr 17, 2015 at 3:02 PM, Tyler Baker wrote:
>> Include lib.mk and set TEST_PROGS where appropriate. Skip the install and
>> test
>> case when CROSS_COMPILE is not set.
>>
>> Cc: Andy Lutomirski
>> Signed-off-by: Tyler Baker
>> ---
>>
On Sat, 18 Apr 2015 00:14:36 +0200 Pavel Machek wrote:
> On Thu 2015-04-16 18:03:04, NeilBrown wrote:
> > From: NeilBrown
> >
> > This driver device one local attribute: vbus.
> > Describe that in Documentation/ABI/testing/sysfs-platform/twl4030-usb.
> >
> > Signed-off-by: NeilBrown
> > ---
On 17 April 2015 at 15:27, Andy Lutomirski wrote:
> On Fri, Apr 17, 2015 at 3:24 PM, Tyler Baker wrote:
>> On 17 April 2015 at 15:06, Andy Lutomirski wrote:
>>> On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
Using uname with the processor flag option in some cases can yield
This patch enables intel_powerclamp driver to run on the
next-generation Intel(R) Xeon Phi Microarchitecture
code named "Knights Landing"
Signed-off-by: Dasaratharaman Chandramouli
---
drivers/thermal/intel_powerclamp.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On Fri, Apr 17, 2015 at 3:02 PM, Tyler Baker wrote:
> Include lib.mk and set TEST_PROGS where appropriate. Skip the install and test
> case when CROSS_COMPILE is not set.
>
> Cc: Andy Lutomirski
> Signed-off-by: Tyler Baker
> ---
> tools/testing/selftests/x86/Makefile | 9 +
> 1 file
On Fri, Apr 17, 2015 at 3:24 PM, Tyler Baker wrote:
> On 17 April 2015 at 15:06, Andy Lutomirski wrote:
>> On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
>>> Using uname with the processor flag option in some cases can yield 'unknown'
>>> so lets use the machine flag option as it is
On Fri, 17 Apr 2015, Richard Weinberger wrote:
> SLUB is the unqueued SLAB and SLLB is the library SLAB. :D
Good that this convention is now so broadly known that I did not even
have to explain what it meant. But I think you can give it any name you
want. SLLB was just a way to tersely state how
On Fri, Apr 17, 2015 at 3:04 PM, Linus Torvalds
wrote:
> On Fri, Apr 17, 2015 at 5:42 PM, Andy Lutomirski wrote:
>>
>> Muahaha. The auditors have invaded your system. (I did my little
>> benchmark with a more sensible configuration -- see way below).
>>
>> Can you send the output of:
>>
>> #
On 17 April 2015 at 15:06, Andy Lutomirski wrote:
> On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
>> Using uname with the processor flag option in some cases can yield 'unknown'
>> so lets use the machine flag option as it is deterministic. Add a dependency
>> for all_32 when building on a
On 4/17/15 22:02, Chen Gang wrote:
> On 4/17/15 11:02, Zhang, Sonic wrote:
>> Hi Gang,
>>
>> Please only use the GCC for Blackfin 2013R1 or 2014R1 from
>> https://sourceforge.net/projects/adi-buildroot/files/ . Upstream GCC5 isn't
>> ported to Blackfin properly.
>>
However, I should still try
On Fri, Apr 17, 2015 at 02:46:56PM -0700, Eric Dumazet wrote:
> On Thu, 2015-04-16 at 14:16 +0200, Mateusz Guzik wrote:
> > Hi,
> >
> > Currently obtaining a new file descriptor results in locking fdtable
> > twice - once in order to reserve a slot and second time to fill it
>
> ...
>
>
> >
On 17 April 2015 at 15:08, Andy Lutomirski wrote:
> On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
>> If the CROSS_COMPILE is set have no dependency on all.
>
> You mean "remove all's dependency on all_32 and all_64", I think.
Yes I'll clean this up.
>
>>
>> Cc: Andy Lutomirski
>>
On Thu 2015-04-16 18:03:04, NeilBrown wrote:
> From: NeilBrown
>
> This driver device one local attribute: vbus.
> Describe that in Documentation/ABI/testing/sysfs-platform/twl4030-usb.
>
> Signed-off-by: NeilBrown
> ---
> .../ABI/testing/sysfs-platform-twl4030-usb |8
>
On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
> If the CROSS_COMPILE is set have no dependency on all.
You mean "remove all's dependency on all_32 and all_64", I think.
>
> Cc: Andy Lutomirski
> Signed-off-by: Tyler Baker
> ---
> tools/testing/selftests/x86/Makefile | 6 +-
> 1
On Fri, Apr 17, 2015 at 3:01 PM, Tyler Baker wrote:
> Using uname with the processor flag option in some cases can yield 'unknown'
> so lets use the machine flag option as it is deterministic. Add a dependency
> for all_32 when building on a x86 64 bit host so that both bitnesses are
> built in
On Fri, Apr 17, 2015 at 5:42 PM, Andy Lutomirski wrote:
>
> Muahaha. The auditors have invaded your system. (I did my little
> benchmark with a more sensible configuration -- see way below).
>
> Can you send the output of:
>
> # auditctl -s
> # auditctl -l
# auditctl -s
enabled 1
flag 1
Remove subdir from DEPS as it is already created at runtime. Without this,
make install fails.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/exec/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/exec/Makefile
Include lib.mk and set TEST_PROGS where appropriate. Skip the install and test
case when CROSS_COMPILE is not set.
Cc: Andy Lutomirski
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 9 +
1 file changed, 9 insertions(+)
diff --git
When the host's C compiler is clang, and when attempting to
cross-compile Linux e.g. to MIPS with mipsel-linux-gcc, the Makefile
would incorrectly detect the use of clang, which resulted in
clang-specific flags being passed to mipsel-linux-gcc.
This can be verified under Debian by installing the
If the CROSS_COMPILE is set have no dependency on all.
Cc: Andy Lutomirski
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/Makefile
b/tools/testing/selftests/x86/Makefile
Using uname with the processor flag option in some cases can yield 'unknown'
so lets use the machine flag option as it is deterministic. Add a dependency
for all_32 when building on a x86 64 bit host so that both bitnesses are
built in this case.
Cc: Andy Lutomirski
Signed-off-by: Tyler Baker
On 15/04/17, Peter Zijlstra wrote:
> On Fri, Apr 17, 2015 at 11:42:50AM -0400, Richard Guy Briggs wrote:
> > On 15/04/17, Peter Zijlstra wrote:
> > > On Fri, Apr 17, 2015 at 03:35:54AM -0400, Richard Guy Briggs wrote:
> > > > Added the macro CLONE_NEW_MASK_ALL to refer to all CLONE_NEW* flags.
> >
Set TEST_PROGS so that kdbus-test is installed.
Cc: Greg Kroah-Hartman
Signed-off-by: Tyler Baker
---
tools/testing/selftests/kdbus/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/kdbus/Makefile
b/tools/testing/selftests/kdbus/Makefile
index
The ftrace test requires the directory test.d and all of it's contents to be
present during execution. Use TEST_DIRS to ensure this is copied to the
INSTALL_PATH.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/ftrace/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git
The breakpoints test should only should be executed on x86 targets, so lets
emit a skip and omit the installation when ARCH != x86.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/breakpoints/Makefile | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
This patch set fixes various issues observed when cross building and
installing selftests.
As I began investigating improving the test output format, I performed an
audit of the current tests to ensure all tests were able to execute on various
target architectures. I found that some tests did not
Loop over all TEST_DIRS and recursively copy them to the INSTALL_PATH. Tests
such as ftrace require a directory and all of it's contents to execute the
test properly, thus these directories and files need to be copied when we
perform an install.
Signed-off-by: Tyler Baker
---
On Thu, 2015-04-16 at 14:16 +0200, Mateusz Guzik wrote:
> Hi,
>
> Currently obtaining a new file descriptor results in locking fdtable
> twice - once in order to reserve a slot and second time to fill it
...
> void __fd_install(struct files_struct *files, unsigned int fd,
>
Havoc Pennington wrote:
> Hi,
>
> On Fri, Apr 17, 2015 at 3:27 PM, James Bottomley
> wrote:
>>
>> This is why I think kdbus is a bad idea: it solidifies as a linux kernel
>> API something which runs counter to granular OS virtualization (and
>> something which caused Windows to fall behind
On Fri, Apr 17, 2015 at 2:28 PM, Linus Torvalds
wrote:
> On Fri, Apr 17, 2015 at 4:39 PM, Andy Lutomirski wrote:
>>
>> On my box, vclock_gettime using kvm-clock is about 40 ns. An empty
>> syscall is about 33 ns. clock_gettime *should* be around 17 ns.
>>
>> The clock_gettime syscall is about
On 04/16/2015 11:20 AM, Vince Weaver wrote:
The rdpmc instruction allows reading performance counters directly
from usersapce. Prior to Linux 4.0 any process could use this
instruction when a perf event was running, even if the process itself
did not have any open. The following changesets
On Fri, Apr 17, 2015 at 4:39 PM, Andy Lutomirski wrote:
>
> On my box, vclock_gettime using kvm-clock is about 40 ns. An empty
> syscall is about 33 ns. clock_gettime *should* be around 17 ns.
>
> The clock_gettime syscall is about 73 ns.
>
> Could we figure out why clock_gettime (the syscall)
On Fri, Apr 17, 2015 at 01:13:18PM -0400, Pranith Kumar wrote:
> On Fri, Apr 17, 2015 at 12:15 PM, Paul E. McKenney
> wrote:
> > Sounds like a good thought for a separate patch. Please take a look
> > through the rest of the documentation -- this might well be the right
> > place for such an
Hi Linus,
>> accepting all flags regardless was an oversight on my part in the first
>> place. What this patch tried to do is to limit it to what userspace is
>> currently actually using. My mistake was to look only at BlueZ 5.x userspace
>> and not at BlueZ 4.x userspace.
>
> So what about
On Fri, 2015-04-17 at 11:50 +0100, Peter Griffin wrote:
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> +config CLKSRC_ST_LPC_CLOCK
> + bool
> + depends on ARCH_STI
> + select CLKSRC_OF if OF
> + help
> + Enable this option to use the Low Power
Shaohua Li writes:
>> Also, Jens or Shaohua or anyone, please review my blk-mq plug fix (patch
>> 1/2 of aforementioned thread). ;)
>
> You are not alone :), I posted 2 times too
> http://marc.info/?l=linux-kernel=142627559617005=2
Oh, sorry! I think Jens had mentioned that you had a patch
>> Do you mean like this?
>>
>> #define SUBSYS_TAG_COUNT(_tag) (CGROUP_ ## _tag ## _END - CGROUP_ ##
>> _tag ## _START)
>>
>> That's fine I guess, I just wanted to match CGROUP_SUBSYS_COUNT in
>> semantics, but I'll do that if you prefer it that way.
>
> Not even that, just do it manually.
>
>
On Fri, Apr 17, 2015 at 4:35 PM, Marcel Holtmann wrote:
>
> accepting all flags regardless was an oversight on my part in the first
> place. What this patch tried to do is to limit it to what userspace is
> currently actually using. My mistake was to look only at BlueZ 5.x userspace
> and not
On Fri, Apr 17, 2015 at 04:54:40PM -0400, Jeff Moyer wrote:
> Shaohua Li writes:
>
> > Current code looks like inner plug gets flushed with a
> > blk_finish_plug(). Actually it's a nop. All requests/callbacks are added
> > to current->plug, while only outmost plug is assigned to current->plug.
>
On 17 April 2015 at 17:34, Jiri Olsa wrote:
> On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote:
>> When building perf with perl or python support it implicitly gets linked
>> with the -export-dynamic linker option through the additional linker
>> flags, namely with -Wl,-E via perl
On Sat, Apr 18, 2015 at 06:48:55AM +1000, Aleksa Sarai wrote:
> Do you mean like this?
>
> #define SUBSYS_TAG_COUNT(_tag) (CGROUP_ ## _tag ## _END - CGROUP_ ##
> _tag ## _START)
>
> That's fine I guess, I just wanted to match CGROUP_SUBSYS_COUNT in
> semantics, but I'll do that if you prefer it
Shaohua Li writes:
> Current code looks like inner plug gets flushed with a
> blk_finish_plug(). Actually it's a nop. All requests/callbacks are added
> to current->plug, while only outmost plug is assigned to current->plug.
> So inner plug always has empty request/callback list, which makes
>
>> >> Do you also want me to completely drop the COUNT macro? IMO it makes
>> >> the CGROUP__COUNT consolidation much nicer.
>> >
>> > What's wrong with simply having start and end tags?
>>
>> Because you'd have to write (CGROUP_TAG_END - CGROUP_TAG_START) every
>> time? It's a small addition and
On Sat, Apr 18, 2015 at 06:35:41AM +1000, Aleksa Sarai wrote:
> >> Do you also want me to completely drop the COUNT macro? IMO it makes
> >> the CGROUP__COUNT consolidation much nicer.
> >
> > What's wrong with simply having start and end tags?
>
> Because you'd have to write (CGROUP_TAG_END -
On Fri, Apr 17, 2015 at 1:18 PM, Marcelo Tosatti wrote:
> On Fri, Apr 17, 2015 at 09:57:12PM +0200, Paolo Bonzini wrote:
>>
>>
>> >> From 4eb9d7132e1990c0586f28af3103675416d38974 Mon Sep 17 00:00:00 2001
>> >> From: Paolo Bonzini
>> >> Date: Fri, 17 Apr 2015 14:57:34 +0200
>> >> Subject: [PATCH]
Hi Geert,
>>> net/bluetooth/mgmt.c: In function ‘read_local_oob_ext_data_complete’:
>>> net/bluetooth/mgmt.c:6474: warning: ‘r256’ may be used uninitialized in
>>> this function
>>> net/bluetooth/mgmt.c:6474: warning: ‘h256’ may be used uninitialized in
>>> this function
>>>
>> Do you also want me to completely drop the COUNT macro? IMO it makes
>> the CGROUP__COUNT consolidation much nicer.
>
> What's wrong with simply having start and end tags?
Because you'd have to write (CGROUP_TAG_END - CGROUP_TAG_START) every
time? It's a small addition and it makes referencing
Hi Linus,
>> okay. I only looked at BlueZ 5.x and that might have been my mistake. Let me
>> check this and fix this properly.
>
> Why not just revert that commit. It looks like garbage. It has odd code like
>
> + u32 valid_flags = 0;
> + ci->flags = session->flags & valid_flags;
>
While it is not used by newer userspace anymore, the older userspace was
utilizing HIDP_VIRTUAL_CABLE_UNPLUG and HIDP_BOOT_PROTOCOL_MODE flags
when adding a new HIDP connection.
The flags validation is important, but we can not break older userspace
and with that allow providing these flags even
1 - 100 of 1674 matches
Mail list logo
