Hi Pan,
On Tue, Jul 07, 2015 at 08:43:26PM +0800, Pan Xinhui wrote:
> @@ -364,19 +363,24 @@ static u32 get_cur_val(const struct cpumask *mask)
>
> static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
> {
> - struct acpi_cpufreq_data *data = per_cpu(acfreq_data, cpu);
> + struct
On Tue, Jul 07, 2015 at 06:30:30PM +0200, Oleg Nesterov wrote:
> On 07/06, Frederic Weisbecker wrote:
> >
> > The call_usermodehelper_exec_[a]sync() kernel threads are created by
> > khelper precisely because
>
> I think khelper should simply die. It doesn't make any sense today,
> kmod.c should
With the exception of mlockall() none of the mlock family of system
calls take a flags argument so they are not extensible. A later patch
in this set will extend the mlock family to support a middle ground
between pages that are locked and faulted in immediately and unlocked
pages. To pave the
The cost of faulting in all memory to be locked can be very high when
working with large mappings. If only portions of the mapping will be
used this can incur a high penalty for locking.
For the example of a large file, this is the usage pattern for a large
statical language model (probably
The analog output range is not programmable, but the ranges for each of
the two analog output channels are settable via jumpers. These jumper
settings are not readable by the driver. The driver
provides a range table containing all the possible internal ranges
(+/-10V, +/-5V, 0-10V, 0-5V) to
This introduces a new helper and switches current users to use it. All patches
are compiled tested, kmemleak is tested by its own test suit.
Changelog v5:
- remove already applied patches (hexdump)
- postpone patch for saa7164 since conficts (needs investigation)
- rebase on top of recent
Instead of custom approach let's use recently introduced seq_hex_dump() helper.
Signed-off-by: Andy Shevchenko
---
mm/kmemleak.c | 21 ++---
1 file changed, 6 insertions(+), 15 deletions(-)
diff --git a/mm/kmemleak.c b/mm/kmemleak.c
index cf79f11..b034c62 100644
---
The new seq_hex_dump() is a complete analogue of print_hex_dump().
We have few users of this functionality already. It allows to reduce their
codebase.
Signed-off-by: Andy Shevchenko
---
fs/seq_file.c| 42 ++
include/linux/seq_file.h | 4
On 07/07/2015 05:43 AM, Mike Galbraith wrote:
On Tue, 2015-07-07 at 06:01 +0200, Mike Galbraith wrote:
On Mon, 2015-07-06 at 15:41 -0400, Josef Bacik wrote:
So the NO_WAKE_WIDE_IDLE results are very good, almost the same as the
baseline with a slight regression at lower RPS and a slight
Instead of custom approach let's use recently introduced seq_hex_dump() helper.
In one case it changes the output from
to
though it seems it
Instead of custom approach let's use recently introduced seq_hex_dump() helper.
Acked-by: Ingo Tuchscherer
Signed-off-by: Andy Shevchenko
---
drivers/s390/crypto/zcrypt_api.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/s390/crypto/zcrypt_api.c
The cost of faulting in all memory to be locked can be very high when
working with large mappings. If only portions of the mapping will be
used this can incur a high penalty for locking.
Now that we have the new VMA flag for the locked but not present state,
expose it as an mmap option like
Instead of custom approach let's use recently introduced seq_hex_dump() helper.
Signed-off-by: Andy Shevchenko
---
drivers/net/wireless/ath/wil6210/debugfs.c | 35 ++
1 file changed, 7 insertions(+), 28 deletions(-)
diff --git
Instead of custom approach let's use recently introduced seq_hex_dump() helper.
Acked-by: Tadeusz Struk
Signed-off-by: Andy Shevchenko
---
drivers/crypto/qat/qat_common/adf_transport_debug.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git
ests on tree/branch linus/master
# extra tests on tree/branch next/master
git bisect bad 8e551e96341aa57779ea93a87c857ae61a057f11 # 01:02 0-
19 Add linux-next specific files for 20150707
This script may reprodu
With the refactored mlock code, introduce new system calls for mlock,
munlock, and munlockall. The new calls will allow the user to specify
what lock states are being added or cleared. mlock2 and munlock2 are
trivial at the moment, but a follow on patch will add a new mlock state
making them
mlock() allows a user to control page out of program memory, but this
comes at the cost of faulting in the entire mapping when it is
allocated. For large mappings where the entire area is not necessary
this is not ideal. Instead of forcing all locked pages to be present
when they are allocated,
Test the mmap() flag, and the mlockall() flag. These tests ensure that
pages are not faulted in until they are accessed, that the pages are
unevictable once faulted in, and that VMA splitting and merging works
with the new VM flag. The second test ensures that mlock limits are
respected. Note
On 02/07/2015 at 18:06:42 +0200, David Dueck wrote :
> Not all gpio banks are necessarily enabled, in the current code this can
> lead to null pointer dereferences.
>
[...]
>
> Signed-off-by: David Dueck
> CC: Nicolas Ferre
> CC: Alexandre Belloni
> CC: Ludovic Desroches
> CC: Boris
On Tue, Jul 07, 2015 at 06:36:53PM +0200, Thomas Huth wrote:
> On Thu, 2 Jul 2015 11:32:52 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Jul 02, 2015 at 11:12:56AM +0200, Greg Kurz wrote:
> > > On Thu, 2 Jul 2015 08:01:28 +0200
> > > "Michael S. Tsirkin" wrote:
> ...
> > > > Yea, well -
On 7/7/15 10:27 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
wrote:
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
Occasionally both MSI and INTx bits in the interrupt decode register are
set at once by the Xilinx AXI PCIe Bridge, so the MSI flag in the
interrupt message should be checked to ensure that the correct handler is
used.
If this check is not in place and the interrupt message type is MSI, the
INTx
>>
>> Well, the checkpatch.pl reports were all style (and mostly whitespace);
>> roughly 3000 of them against 3000 lines of code :-/. I did review the
>> code, looking for areas where I thought it would badly cram into the
>> kernel, and I adjusted the few I found (and sent changes upstream).
>
On 7/7/15 10:24 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern wrote:
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you
This patch set adds support for the Dialog DA9150 Fuel-Gauge.
In this patch set the following is provided:
- MFD Core and DT bindings updates.
- Power Supply Fuel-Gauge support and DT bindings documentation.
This patch set is baselined against the v4.2-rc1 kernel version.
Changes in v3:
-
Signed-off-by: Adam Thomson
---
Changes in v3:
- N/A
Changes in v2:
- N/A
.../devicetree/bindings/power/da9150-fg.txt| 23 ++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/da9150-fg.txt
diff --git
Signed-off-by: Adam Thomson
---
Changes in v3:
- Initial version.
Changes in v2:
- N/A
drivers/mfd/da9150-core.c | 35 +--
1 file changed, 5 insertions(+), 30 deletions(-)
diff --git a/drivers/mfd/da9150-core.c b/drivers/mfd/da9150-core.c
index
On Thu, 2 Jul 2015 11:32:52 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Jul 02, 2015 at 11:12:56AM +0200, Greg Kurz wrote:
> > On Thu, 2 Jul 2015 08:01:28 +0200
> > "Michael S. Tsirkin" wrote:
...
> > > Yea, well - support for legacy BE guests on the new LE hosts is
> > > exactly the motivation
This commit defines the API headers for guest debugging. There are two
architecture specific debug structures:
- kvm_guest_debug_arch, allows us to pass in HW debug registers
- kvm_debug_exit_arch, signals exception and possible faulting address
The type of debugging being used is controlled
This introduces a level of indirection for the debug registers. Instead
of using the sys_regs[] directly we store registers in a structure in
the vcpu. The new kvm_arm_reset_debug_ptr() sets the debug ptr to the
guest context.
Because we no longer give the sys_regs offset for the
Signed-off-by: Adam Thomson
---
Changes in v3:
- Use DEFINE_RES_IRQ_NAMED() helper for defining FG IRQ resource.
- Unwanted new line & comments removed.
- Remove gotos which can be replaced with straight forward return calls.
- Add enum for indexing MFD cells list, which is used to assign
This adds support for SW breakpoints inserted by userspace.
We do this by trapping all guest software debug exceptions to the
hypervisor (MDCR_EL2.TDE). The exit handler sets an exit reason of
KVM_EXIT_DEBUG with the kvm_debug_exit_arch structure holding the
exception syndrome information.
It
Signed-off-by: Adam Thomson
---
Changes in v3:
- Removed use of temp callback function, at request of Lee Jones.
- Comment added to clarify limitation of temperature reading functionality
that remains.
Changes in v2:
- Moved temp callback function prototype to be part of power fuel-gauge
Signed-off-by: Adam Thomson
Acked-by: Lee Jones
---
Changes in v3:
- Removal of unwanted new-line.
- Flesh out example bindings usage.
Changes in v2:
- N/A
Documentation/devicetree/bindings/mfd/da9150.txt | 25 +---
1 file changed, 22 insertions(+), 3 deletions(-)
This adds support for single-stepping the guest. To do this we need to
manipulate the guests PSTATE.SS and MDSCR_EL1.SS bits to trigger
stepping. We take care to preserve MDSCR_EL1 and trap access to it to
ensure we don't affect the apparent state of the guest.
As we have to enable trapping of
When referencing other DT bindings documentation, use relative
path rather than absolute.
Signed-off-by: Adam Thomson
---
Changes in v3:
- Initial version.
Changes in v2:
- N/A
Documentation/devicetree/bindings/mfd/da9150.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Hi folks,
I'm writing a kernel module that creates a virtual network device with
rtnl_link_register. At initialization time, it creates a UDP socket
with sock_create_kern. On ndo_start_xmit, it passes the data of the
skb to the UDP socket's sendmsg, after some minimal crypto and
processing. The
- On Jul 7, 2015, at 3:29 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Tue, Jul 07, 2015 at 02:59:06PM +0930, Arthur Marsh wrote:
>> I had a single, non-reproducible case of the same lock-up happening on my
>> other machine running the Linus git head kernel in 64-bit mode.
>
> Hmm,
On 07/06, Frederic Weisbecker wrote:
>
> The call_usermodehelper_exec_[a]sync() kernel threads are created by
> khelper precisely because
I think khelper should simply die. It doesn't make any sense today,
kmod.c should use some system wq instead. But see below.
> Not only useless it even breaks
This includes trace points for:
kvm_arch_setup_guest_debug
kvm_arch_clear_guest_debug
I've also added some generic register setting trace events and also a
trace point to dump the array of hardware registers.
Signed-off-by: Alex Bennée
---
v3
- add trace event for debug access.
-
Finally advertise the KVM capability for SET_GUEST_DEBUG. Once arm
support is added this check can be moved to the common
kvm_vm_ioctl_check_extension() code.
Signed-off-by: Alex Bennée
Acked-by: Christoffer Dall
---
v3:
- separated capability check from previous patches
- moved into arm64
This is a pre-cursor to sharing the code with the guest debug support.
This replaces the big macro that fishes data out of a fixed location
with a more general helper macro to restore a set of debug registers. It
uses macro substitution so it can be re-used for debug control and value
registers.
Bring into line with the comments for the other structures and their
KVM_EXIT_* cases. Also update api.txt to reflect use in kvm_run
documentation.
Signed-off-by: Alex Bennée
Reviewed-by: David Hildenbrand
Reviewed-by: Andrew Jones
Acked-by: Christoffer Dall
---
v2
- add comments for
This adds support for userspace to control the HW debug registers for
guest debug. In the debug ioctl we copy an IMPDEF registers into a new
register set called host_debug_state.
We use the recently introduced vcpu parameter debug_ptr to select which
register set is copied into the real registers
This is a precursor for later patches which will need to do more to
setup debug state before entering the hyp.S switch code. The existing
functionality for setting mdcr_el2 has been moved out of hyp.S and now
uses the value kept in vcpu->arch.mdcr_el2.
As the assembler used to previously mask and
This commit adds a stub function to support the KVM_SET_GUEST_DEBUG
ioctl. Any unsupported flag will return -EINVAL. For now, only
KVM_GUESTDBG_ENABLE is supported, although it won't have any effects.
Signed-off-by: Alex Bennée .
Reviewed-by: Christoffer Dall
---
v2
- simplified form of the
Hi David,
On Mon, Jul 06, 2015 at 08:48:26PM +0200, David Herrmann wrote:
> Hi
>
> On Sun, Jun 28, 2015 at 3:17 PM, Sergei Zviagintsev wrote:
> > Hi,
> >
> > Main points here are to use conventional types, rewrite tests in obvious
> > way, add couple of new WARN_ONs and do a bit more work in
On Tue, Jul 07, 2015 at 12:17:57PM -0400, Vivien Didelot wrote:
> Hi Andrew, Scott,
> Does this fixup http://ix.io/jxq look good to you?
Yes, that looks good.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
wrote:
> Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
>> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
>> > On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
>> > Would it make more sense to have a
On Tue, Jul 07, 2015 at 05:34:13PM +0200, Peter Zijlstra wrote:
> On Tue, Jul 07, 2015 at 03:34:22PM +0200, Frederic Weisbecker wrote:
> > Imagine the following rounds:
> >
> > utime:2 stime:2 rtime:4 --> prev->utime = 2 prev->stime = 2
> >
> > utime:2 stime:6 rtime:8 --> prev->utime = 2
Hypervisor callback interrupts are only accounted on Xen/Hyper-V. There is
no point in having always-zero HYP: line on other hypervisors or bare
metal. Print the line only if HYPERVISOR_CALLBACK_VECTOR was allocated.
Reported-by: Radim Krčmář
Signed-off-by: Vitaly Kuznetsov
---
Changes in v2:
-
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> > On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> > Would it make more sense to have a new syscall instead? You could
> > even still use nlattr formatting
Hi Roger,
On Tue, Jul 07, 2015 at 12:37:31PM +0300, Roger Quadros wrote:
> Hi Dmitry,
>
> On 07/07/15 03:27, Dmitry Torokhov wrote:
> >The binding specification says that "touchscreen-size-x" and "-y" specify
> >horizontal and vertical resolution of the touchscreen and therefore maximum
>
On 07/07/2015 05:01 PM, Dan Carpenter wrote:
On Tue, Jul 07, 2015 at 04:02:51PM +0200, Robert Baldyga wrote:
Should use usb_ep_set_maxpacket_limit instead of setting
maxpacket value manually.
This is a behavior change, right, since now we're setting
ep->ep.maxpacket and
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern wrote:
> On 7/7/15 9:56 AM, Andy Lutomirski wrote:
>>
>> Netlink is fine for these use cases (if they were related to the
>> netns, not the pid ns or user ns), and it works. It's still tedious
>> -- I bet that if you used a syscall, the user code would
Mazhar Rana wrote:
>From: Mazhar Rana
>
>When "primary_reselect" is set to "failure", primary interface should
>not become active until current active slave is down. But if we set first
>member of bond device as a "primary" interface and "primary_reselect"
>is set to "failure" then whenever
Hi Guenter, Andrew,
- On Jul 7, 2015, at 12:07 PM, Andrew Lunn and...@lunn.ch wrote:
>> Indeed, I intentionally kept it as is, since the 88E6352 datasheet is not
>> really clear about this. I see that the register 0x09 (called
>> GLOBAL_VTU_DATA_8_11 in mv88e6xxx.h) only contains VID
Hi Andrew, Scott,
On Jul 6, 2015, at 11:46 PM, Scott Feldman sfel...@gmail.com wrote:
> On Mon, Jul 6, 2015 at 7:00 PM, Andrew Lunn wrote:
>> On Tue, Jul 07, 2015 at 01:38:04AM +0200, Andrew Lunn wrote:
>>> On Sun, Jul 05, 2015 at 10:14:50PM -0400, Vivien Didelot wrote:
>>> > Hi all,
>>> >
>>>
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you used a syscall, the user code would be
considerable shorter, though. :)
How would this be a
> I can't remember ever changing or explicitly preserving the commit date.
> I don't think I care enough.
Would any more software developers and maintainers like to share
their experiences around such details?
When do commit timestamps become relevant as a documentation item
for contribution
On Fri, Jun 26, 2015 at 12:12:06PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2015-06-24 at 18:22 -0700, Luis R. Rodriguez wrote:
> > Although I had test compiled this before just to be safe I went ahead and
> > successfully test-compiled this set with allmodconfig, specially since I've
> >
Em Tue, Jul 07, 2015 at 05:36:14PM +0200, Peter Zijlstra escreveu:
> On Tue, Jul 07, 2015 at 10:44:37AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jul 07, 2015 at 10:25:52AM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Tue, Jul 07, 2015 at 11:36:39AM +0300, Adrian Hunter escreveu:
>
> Indeed, I intentionally kept it as is, since the 88E6352 datasheet is not
> really clear about this. I see that the register 0x09 (called
> GLOBAL_VTU_DATA_8_11 in mv88e6xxx.h) only contains VID priority related bits
> in
> 15:12, in my case. As bits 11:0 are reserved, I suspect that the
On 07/07/2015 08:52 AM, Vivien Didelot wrote:
Hi Andrew,
On Jul 6, 2015, at 10:08 PM, Andrew Lunn and...@lunn.ch wrote:
+static int _mv88e6xxx_vtu_getnext(struct dsa_switch *ds, u16 vid,
+ struct mv88e6xxx_vtu_entry *entry)
+{
+ int ret, i;
+
+ ret
On Tue, Jul 07, 2015 at 11:13:30AM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 07, 2015 at 11:50:12AM +0200, Luis R. Rodriguez wrote:
> > mcgrof@ergon ~/linux-next (git::kill-mtrr)$ git grep ioremap_nocache
> > drivers/| wc -l
> > 359
>
> Yes, it's because we have:
> (a) LDD telling
If the "comedi" module has been loaded with the
"comedi_num_legacy_minors" module parameter set to a non-zero value,
some reserved comedi devices get created. These can be attached to a
low-level comedi driver using the `COMEDI_DEVCONFIG` ioctl command,
which checks for the `CAP_SYS_ADMIN`
On Tue, Jul 7, 2015 at 4:12 AM, Ingo Molnar wrote:
>
> So this looks mostly problem free on my boxen, except this warning triggers:
>
> Adding 3911820k swap on /dev/sda2. Priority:-1 extents:1 across:3911820k
> capability: warning: `dbus-daemon' uses 32-bit capabilities (legacy support
> in
On 06/07/15 20:52, Stephen Boyd wrote:
On 07/03/2015 07:52 AM, Sudeep Holla wrote:
Hi Stephen,
Thanks for the review.
On 02/07/15 18:23, Stephen Boyd wrote:
On 06/08, Sudeep Holla wrote:
[...]
+
+clk = devm_clk_register(dev, >hw);
+if (!IS_ERR(clk) && max)
+
ests on tree/branch linus/master
# extra tests on tree/branch next/master
git bisect bad 8e551e96341aa57779ea93a87c857ae61a057f11 # 00:00 0-
1 Add linux-next specific files for 20150707
This script may reprodu
On 07/07/2015 04:53 PM, Dan Carpenter wrote:
On Tue, Jul 07, 2015 at 04:02:49PM +0200, Robert Baldyga wrote:
diff --git a/drivers/usb/gadget/function/f_fs.c
b/drivers/usb/gadget/function/f_fs.c
index 6e7be91..966b214 100644
--- a/drivers/usb/gadget/function/f_fs.c
+++
Peter Zijlstra wrote on 07/07/15 16:59:
Do you have a serial cable between those machines? serial console output
will allow capturing more complete traces than these pictures can and
might also aid in capturing some extra debug info.
In any case, I'll go try and build some debug code.
I
On Tue, 7 Jul 2015 18:10:41 +0800
Chunyan Zhang wrote:
> output_stm is a link which is used to connect trace event
> logging with STMs, will be used in the upcoming patches.
>
> Signed-off-by: Chunyan Zhang
> ---
> include/linux/trace_events.h | 8
> 1 file changed, 8 insertions(+)
On 07/07/2015 05:37 PM, Roger Quadros wrote:
On 07/07/15 17:35, Roger Quadros wrote:
On 07/07/15 17:33, Marc Kleine-Budde wrote:
On 07/07/2015 04:27 PM, Roger Quadros wrote:
From: "J.D. Schroeder"
The previous change 3973c526ae9c (net: can: c_can: Disable pins when
CAN interface
is down)
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
>> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
>> > Currently we use the proc file system, where all information are
>> > presented in text files, what is convenient for
blkg_create() allows NULL ->pd_init_fn() but blkcg_activate_policy()
doesn't. As both in-kernel policies implement ->pd_init_fn, it
currently doesn't break anything. Update blkcg_activate_policy() so
that its behavior is consistent with blkg_create().
Signed-off-by: Tejun Heo
Cc: Vivek Goyal
With the recent addition of alloc and free methods, things became
messier. This patch reorganizes them according to the followings.
* ->pd_alloc_fn()
Responsible for allocation and static initializations - the ones
which can be done independent of where the pd might be attached.
*
On Tue, Jul 07, 2015 at 10:03:15AM +0530, Maninder Singh wrote:
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 1ef2940..53d57db 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -51,8 +51,9 @@ int show_unhandled_signals = 1;
> /*
> *
The newly added ->pd_alloc_fn() and ->pd_free_fn() deal with pd
(blkg_policy_data) while the older ones use blkg (blkcg_gq). As using
blkg doesn't make sense for ->pd_alloc_fn() and after allocation pd
can always be mapped to blkg and given that these are policy-specific
methods, it makes sense
On Tue, Jul 07, 2015 at 04:04:57PM +0200, Pali Rohár wrote:
> On Monday 06 July 2015 15:39:37 Darren Hart wrote:
> > On Mon, Jul 06, 2015 at 12:08:55PM +0200, Pali Rohár wrote:
> > > Make sure that before initializing SMBIOS call input buffer does not
> > > contain any garbage (e.g. values from
Hi Andrew,
On Jul 6, 2015, at 10:08 PM, Andrew Lunn and...@lunn.ch wrote:
>> +static int _mv88e6xxx_vtu_getnext(struct dsa_switch *ds, u16 vid,
>> + struct mv88e6xxx_vtu_entry *entry)
>> +{
>> +int ret, i;
>> +
>> +ret = _mv88e6xxx_vtu_wait(ds);
>> +if
When blkcg_init_queue() fails midway after creating a new blkg, it
performs kfree() directly; however, this doesn't free the policy data
areas. Make it use blkg_free() instead. In turn, blkg_free() is
updated to handle root request_list special case.
While this fixes a possible memory leak,
Because percpu allocator couldn't do non-blocking allocations,
blk-throttle was forced to implement an ad-hoc asynchronous allocation
mechanism for its percpu stats for cases where blkg's (blkcg_gq's) are
allocated from an IO path without sleepable context.
Now that percpu allocator can handle
A blkg (blkcg_gq) represents the relationship between a cgroup and
request_queue. Each active policy has a pd (blkg_policy_data) on each
blkg. The pd's were allocated by blkcg core and each policy could
request to allocate extra space at the end by setting
blkcg_policy->pd_size larger than the
Since ec13b1d6f0a0 ("blkcg: always create the blkcg_gq for the root
blkcg"), a request_list always has its blkg associated. Drop
unnecessary rl->blkg NULL test from blk_put_rl().
Signed-off-by: Tejun Heo
Cc: Vivek Goyal
---
include/linux/blk-cgroup.h | 3 +--
1 file changed, 1 insertion(+), 2
This is v2 of blkcg_policy methods cleanup patchset. Changes from the
last take [L] are
* Rebased on top of v4.2-rc1 and other pending patches. v4.2-rc1
added a patch to add per-blkcg policy data which is allocated by
blkcg core as per-blkcg_gq policy data was before this patchset
making
On Thu, 2015-06-18 at 12:48 -0700, Stephen Boyd wrote:
> On 03/31, Andy Shevchenko wrote:
> > diff --git a/include/linux/clk-provider.h b/include/linux/clk
> > -provider.h
> > index 5591ea7..20b0b67 100644
> > --- a/include/linux/clk-provider.h
> > +++ b/include/linux/clk-provider.h
> > @@ -353,6
Already fixed in linux-next. Sorry for the noise.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
HI Vinod,
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Saturday, June 27, 2015 8:11 PM
> To: Appana Durga Kedareswara Rao
> Cc: dan.j.willi...@intel.com; Michal Simek; Soren Brinkmann; Anirudha
> Sarangi; Punnaiah Choudary Kalluri;
On Tue, 2015-07-07 at 17:41 +0200, Nicolai Stange wrote:
> Commit 61031952f4c8 ("arch, x86: pmem api for ensuring durability of
> persistent memory updates")
> defined __pmem in include/linux/compiler.h only for the case
> CONFIG_RCU_SPARSE_POINTER=n, probably by accident.
>
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> > Currently we use the proc file system, where all information are
> > presented in text files, what is convenient for humans. But if we need
> > to get information about
Hello,
This is v2 of cfq cgroup writeback patchset. Changes from the last
take[L] are
* Switched from GFP_ATOMIC to GFP_NOWAIT as suggested by Jeff.
* Other misc review points addressed, acks added and rebased.
cfq has always charged all async IOs to the root cgroup. It didn't
have much
Commit 61031952f4c8 ("arch, x86: pmem api for ensuring durability of
persistent memory updates")
defined __pmem in include/linux/compiler.h only for the case
CONFIG_RCU_SPARSE_POINTER=n, probably by accident.
With CONFIG_RCU_SPARSE_POINTER=y a sparse compile gives the error:
Algo self tests are failing for CTR mode with omap-aes driver,
giving the following error:
[ 150.053644] omap_aes_crypt: request size is not exact amount of AES
blocks
[ 150.061262] alg: skcipher: encryption failed on test 5 for ctr-aes-omap:
ret=22
This is because the input length is
If the cfq_queue cached in cfq_io_cq is the oom one, cfq_set_request()
replaces it by invoking cfq_get_queue() again without putting the oom
queue leaking the reference it was holding. While oom queues are not
released through reference counting, they're still reference counted
and this can
On 07/07/2015 17:22, Alex Williamson wrote:
>> > -#define __KVM_HAVE_ARCH_NONCOHERENT_DMA
>> > +#define __KVM_HAVE_ARCH_VFIO_HOOKS
> Do we really want to tie these two things together under something
> that's not strictly a "vfio" option? Legacy assignment also makes use
> of these, as shown in
This is necessary for making async cfq_cgroups per-cfq_group instead
of per-cfq_data. While this change makes cfq_get_queue() perform RCU
locking and look up cfq_group even when it reuses async queue, the
extra overhead is extremely unlikely to be noticeable given that this
is already sitting
cfq_find_alloc_queue() checks whether a queue actually needs to be
allocated, which is unnecessary as its sole caller, cfq_get_queue(),
only calls it if so. Also, the oom queue fallback logic is scattered
between cfq_get_queue() and cfq_find_alloc_queue(). There really
isn't much going on in the
On Tue, Jul 07, 2015 at 02:10:56PM +0200, Fredrik Markström wrote:
> Just to let you know, I've tested your last patch and it solves all my
> original problems (which is should since the code is functionally
> equivalent).
Awesome, I'll add:
Tested-by: Fredrik Markstrom
--
To unsubscribe from
On Tue, Jul 07, 2015 at 10:44:37AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 07, 2015 at 10:25:52AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Jul 07, 2015 at 11:36:39AM +0300, Adrian Hunter escreveu:
> > > To make the event useful for privileged users also, if the
> > >
Up until now, all async IOs were queued to async queues which are
shared across the whole request_queue, which means that blkcg resource
control is completely void on async IOs including all writeback IOs.
It was done this way because writeback didn't support writeback and
there was no way of
501 - 600 of 2298 matches
Mail list logo
