On 09/09/2015 10:40 AM, Kees Cook wrote:
> Re-ping. Can someone pull this into their tree?
>
> -Kees
>
> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook wrote:
>> This adds support for s390 to the seccomp selftests. Some improvements
>> were made to enhance the accuracy of failure reporting, and add
Em Wed, Sep 09, 2015 at 01:06:40PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Sep 08, 2015 at 01:35:10PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Sep 08, 2015 at 01:13:59PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Tue, Sep 08, 2015 at 12:58:31PM -0300, Arnaldo Carval
On 09/09, Linus Torvalds wrote:
>
> On Wed, Sep 9, 2015 at 6:16 AM, Oleg Nesterov wrote:
> >
> > Again, rightly or not I believe that FIFO makes task_work_add() more useful.
> > Perhaps I am wrong, so far I can only provide the artificial examples...
>
> I'd rather wait until somebody has a real u
On Wed, Sep 9, 2015 at 9:29 AM, Ross Zwisler
wrote:
> Linus, would you consider applying this to the v4.3 merge tree?
Done.
Linus
--
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
On Wed, Sep 09, 2015 at 09:37:51AM -0700, Kees Cook wrote:
> On Wed, Sep 9, 2015 at 9:09 AM, Daniel Borkmann wrote:
> > On 09/09/2015 06:07 PM, Alexei Starovoitov wrote:
> >>
> >> On Wed, Sep 09, 2015 at 09:50:35AM -0600, Tycho Andersen wrote:
> >
> > [...]
> >>>
> >>> Thoughts?
> >>
> >>
> >> Ple
On Wed, 2015-09-09 at 12:36 -0400, Tejun Heo wrote:
> On Wed, Sep 09, 2015 at 09:33:52AM -0700, Joe Perches wrote:
> > On Wed, 2015-09-09 at 12:13 +0200, Maurizio Lombardi wrote:
> > > When printing a bitmap using the "%*pb[l]" printk format
> > > a 16 bit variable (field_width) is used to store th
On 09/09/2015 10:45 AM, Shuah Khan wrote:
> On 09/09/2015 10:40 AM, Kees Cook wrote:
>> Re-ping. Can someone pull this into their tree?
>>
>> -Kees
>>
>> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook wrote:
>>> This adds support for s390 to the seccomp selftests. Some improvements
>>> were made to e
On Mon, 2015-09-07 at 17:36 +0300, Irina Tirdea wrote:
> After power on, it is recommended that the driver resets the device.
> The reset procedure timing is described in the datasheet and is used
> at device init (before writing device configuration) and
> for power management. It is a sequence of
On Mon, 2015-09-07 at 17:36 +0300, Irina Tirdea wrote:
> Signed-off-by: Irina Tirdea
Acked-by: Bastien Nocera
> ---
> drivers/input/touchscreen/goodix.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/input/touchscreen/goodix.c
> b/drivers/input/t
On Mon, 2015-09-07 at 17:36 +0300, Irina Tirdea wrote:
> Each of the Goodix devices supported by this driver has a fixed size
> for
> the configuration information registers. The size varies depending on
> the
> device and is specified in the datasheet.
>
> Use the proper configuration length as s
On Thu, 2015-07-30 at 11:27 +, Tirdea, Irina wrote:
> I can send some additional patches that will simplify testing the
> configuration update to the Goodix device. I think this feature is
> the easiest
> to test so we can determine if writing to the interrupt pin actually
> works.
> However, e
On Wed, Sep 9, 2015 at 1:32 AM, Miroslav Lichvar wrote:
> On Tue, Sep 08, 2015 at 10:57:06PM -0700, John Stultz wrote:
>> Recently an issue was reported that was difficult to detect except
>> by tweaking the adjtimex tick value, and noticing how quickly the
>> adjustment took to be made:
>>
On 9/9/15 9:38 AM, Murali Karicheri wrote:
On 09/04/2015 11:53 PM, santosh.shilim...@oracle.com wrote:
On 9/4/15 5:46 PM, Murali Karicheri wrote:
To help the user, print the PDSP file name as part of
knav_queue_load_pdsp(). This will be useful for users to know what
version of the firmware is l
(adding Colin and John)
On 09/09/2015 12:41 AM, Shawn Lin wrote:
we found this issue but still exit in lastest kernel. Simply
keep ion_handle_create under mutex_lock to avoid this race.
WARNING: CPU: 2 PID: 2648 at drivers/staging/android/ion/ion.c:512
ion_handle_add+0xb4/0xc0()
ion_handle_add
On Wed, Sep 09, 2015 at 06:43:11PM +1000, Michael Ellerman wrote:
> On Tue, 2015-09-08 at 16:34 +0200, Andrea Arcangeli wrote:
> >
> > I already had a few minor changes queued to be submitted for arm and
> > ppc and a few updates to the selftest.
> >
> > I didn't like that you had to remember run
On Wed, Sep 9, 2015 at 9:56 AM, Shuah Khan wrote:
> On 09/09/2015 10:45 AM, Shuah Khan wrote:
>> On 09/09/2015 10:40 AM, Kees Cook wrote:
>>> Re-ping. Can someone pull this into their tree?
>>>
>>> -Kees
>>>
>>> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook wrote:
This adds support for s390 to
On 09/09/2015 01:12 PM, santosh.shilim...@oracle.com wrote:
On 9/9/15 9:38 AM, Murali Karicheri wrote:
On 09/04/2015 11:53 PM, santosh.shilim...@oracle.com wrote:
On 9/4/15 5:46 PM, Murali Karicheri wrote:
To help the user, print the PDSP file name as part of
knav_queue_load_pdsp(). This will
Commit a2b3471b5b13 ("toshiba_acpi: Use the Hotkey Event Type function
for keymap choosing") changed the *setup_keyboard function to query for
the Hotkey Event Type to help choose the correct keymap, but turns out
that here are certain Toshiba models out there not implementing this
feature, and thu
Commit e1a949c1b988 ("toshiba_acpi: Refactor *{get, set} functions return
value") made changes on the return type of the HCI/SCI functions, but a
typo on the USB Sleep and Music code is always reporting non existent
support for such feature.
This patch corrects the typo, changing an assignment to
On Wed, Sep 9, 2015 at 9:52 AM, Alexei Starovoitov
wrote:
> On Wed, Sep 09, 2015 at 09:37:51AM -0700, Kees Cook wrote:
>> On Wed, Sep 9, 2015 at 9:09 AM, Daniel Borkmann wrote:
>> > On 09/09/2015 06:07 PM, Alexei Starovoitov wrote:
>> >>
>> >> On Wed, Sep 09, 2015 at 09:50:35AM -0600, Tycho Ander
On Wed, Sep 9, 2015 at 1:25 AM, Eric W. Biederman wrote:
> Andy Lutomirski writes:
> > On Tue, Sep 8, 2015 at 4:07 PM, Eric W. Biederman
> > wrote:
>
> >> Perhaps I had missed it but I don't recall capsicum being able to wrap
> >> things like reboot(2).
> >>
> >
> > Ah, so you want to be able t
Hi Thierry,
On Wed, Sep 9, 2015 at 10:11 AM, Thierry Reding
wrote:
> Hi,
>
> There's currently an issue with PCI configuration space accesses on
> Tegra. The PCI host controller driver's ->map_bus() implementation
> remaps I/O memory on-demand to avoid potentially wasting 256 MiB of
> virtual add
These two patches make some changes to the hotkeys code, the first
patch unify the hotkey enabling code, and the second changes the default
hotkey enabling parameter.
Azael Avalos (2):
toshiba_acpi: Unify hotkey enabling functions
toshiba_acpi: Change default Hotkey enabling value
drivers/pl
Currently the driver has two functions enabling hotkeys support,
but these two functions can be merged into one.
This patch merges these two functions, moving some checks to the
*enable_hotkeys function, simplifying code in the process.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshi
Toshiba laptops that feature WMI events for hotkeys were left unsupported
by the toshiba_acpi driver, however, commit a88bc06e5aec ("toshiba_acpi:
Avoid registering input device on WMI event laptops") added hardware
support for such laptops, but the hotkeys are not handled there.
This driver adds
The function toshiba_acpi_setup_keyboard currently has two u32 variables
used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT
query.
This patch removes those two variables, as we already have a global
variable named "hotkey_event_type" and the result of the HCI_SYSTEM_EVENT
q
This patch adds the 0x prefix to the values printed by such function, the
values are already being printed in hex, but without the prefix, causing
confussion, even though the file under Documentation/ABI clearly states
that hey are hex values.
Simply add the 0x prefix to avoid such confussion.
Si
On Wed, Sep 09, 2015 at 10:27:08AM -0700, Kees Cook wrote:
> On Wed, Sep 9, 2015 at 9:52 AM, Alexei Starovoitov
> wrote:
> > On Wed, Sep 09, 2015 at 09:37:51AM -0700, Kees Cook wrote:
> >> On Wed, Sep 9, 2015 at 9:09 AM, Daniel Borkmann
> >> wrote:
> >> > On 09/09/2015 06:07 PM, Alexei Starovoit
On Wed, Sep 09, 2015 at 01:17:11PM +0900, Krzysztof Kozlowski wrote:
> On 09.09.2015 11:26, Andreas Dannenberg wrote:
> > Krzysztof, good observation! In bq2425x_charger.c (formerly known as
> > bq24257_charger.c :) that I worked on the unit used was uA. At that time
> > I did a quick check and the
All make targets support $KCONFIG_CONFIG because they
run scripts/kconf. Make sure merge_config.sh accesses the
correct file in all cases.
Previously this script broke in two different code paths,
one for targets like kvmconfig (which use merge_config.sh -m
then call a target that respects KCONF
merge_config.sh can usefully be applied to a single file.
It implicitly merges with the default configuration.
Signed-off-by: Gabriel de Perthuis
Cc: Michal Marek
---
scripts/kconfig/merge_config.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/merge_confi
The driver currently uses the hotkey enabling value of 0x09 to enable
hotkey events, but windows uses a different value (0x01).
All Toshiba laptops accept the following "hotkey" parameters:
0x01 - Enable hotkey and system events.
0x03 - Enable system events only.
0x09 - Enable hotkey events only.
On 9/8/2015 11:28 AM, David Daney wrote:
> From: David Daney
>
> It is perfectly legitimate for a PCI device to have an
> PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't
> use interrupts, or on PCIe devices, where only MSI/MSI-X are
> supported.
>
> Silence the annoy
On Wed, Sep 09, 2015 at 06:10:22AM +0100, Eduardo Valentin wrote:
> Hi
Hi Eduardo,
> On Thu, Aug 27, 2015 at 11:55:49AM +0100, Javi Merino wrote:
> > From: Ørjan Eide
> >
> > Add a generic thermal cooling device for devfreq, that is similar to
> > cpu_cooling.
> >
> > The device must use devfr
Second attempt at this reply. The first reply was mangled.
On 9/8/2015 11:28 AM, David Daney wrote:
> From: David Daney
>
> It is perfectly legitimate for a PCI device to have an
> PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't
> use interrupts, or on PCIe devices, where o
On 09/09/2015 10:44 AM, Frank Rowand wrote:
Second attempt at this reply. The first reply was mangled.
On 9/8/2015 11:28 AM, David Daney wrote:
From: David Daney
It is perfectly legitimate for a PCI device to have an
PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't
use in
(cc-ing linux-mm)
On 09/09/2015 07:44 AM, Vitaly Wool wrote:
__zone_watermark_ok() does not corrrectly take high-order
CMA pageblocks into account: high-order CMA blocks are not
removed from the watermark check. Moreover, CMA pageblocks
may suddenly vanish through CMA allocation, so let's not
reg
On Wed, 9 Sep 2015, Vlastimil Babka wrote:
> On 09/09/2015 04:01 PM, Christoph Lameter wrote:
> > On Wed, 9 Sep 2015, Nikolay Borisov wrote:
> >
> > What does:
> >
> > echo 1 >trace
> >
> > do? Could crash the sysem due to overload of messages.
>
> Yes I've seen that happen. Did you consider h
-08-27
16:30:01 -0700)
are available in the git repository at:
git://git.infradead.org/linux-mtd.git tags/for-linus-20150909
for you to fetch changes up to 2ff46e6fea6254ac8fa97aeb9c14e51436ab95f6:
mtd: spi-nor: fix NULL dereference when no match found in spi_nor_ids[]
(2015-09-02 16:34:35
As recommended I fixed several coding style issues related with whitespaces.
Signed-off-by: Oscar Forner Martinez
---
fs/isofs/compress.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/fs/isofs/compress.c b/fs/isofs/compress.c
index 5750830..107a078 100644
--- a/
The coding style issue is the white spaces after and before the brackets in the
for. The change in the conditional is to make it consistence with the other
ones in the file. All other conditionals are tested like that.
Signed-off-by: Oscar Forner Martinez
---
fs/isofs/compress.c | 4 ++--
1 fi
Some fixes for coding style issues and consistence in a conditional.
Maitesin (2):
fs: isofs: Fix a coding style issue and change conditional to make it
consistence
fs: isofs: Fix several coding style issues
fs/isofs/compress.c | 13 ++---
1 file changed, 6 insertions(+), 7 delet
Hi,
On 8 September 2015 at 16:46, Heiko Stübner wrote:
>
> Hi Andy,
>
> Am Dienstag, 8. September 2015, 20:43:07 schrieb Andy Yan:
> > rockchip platform have a protocol to pass the the kernel
> > reboot mode to bootloader by some special registers when
> > system reboot.By this way the bootloader
Hi,
On Friday, 28 August 2015, Simon Glass wrote:
>
> Hi Rob,
>
> On 25 August 2015 at 10:22, Rob Herring wrote:
> > On Sat, Aug 15, 2015 at 8:46 AM, Simon Glass wrote:
> >> Hi Rob,
> >>
> >> On 14 August 2015 at 14:29, Rob Herring wrote:
> >>> On Fri, Aug 14, 2015 at 1:34 PM, Simon Glass wro
Hi,
liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
data synchronization library provides read-side access which scales
linearly with the number of cores. It does so by allowing multiple
copies of a given data structure to live at the same time, and by
monitoring the data stru
Hi,
> From: k.kozlowsk...@gmail.com [mailto:k.kozlowsk...@gmail.com] On Behalf
> Of Krzysztof Kozlowski
> Sent: Monday, September 7, 2015 9:28 AM
> To: Pallala, Ramakrishna
> Cc: linux-kernel@vger.kernel.org; linux...@vger.kernel.org;
> devicet...@vger.kernel.org; Sebastian Reichel; Tc, Jenny; An
2015-09-09 11:28 GMT-03:00 Thomas Gleixner :
> B1;2802;0cOn Wed, 9 Sep 2015, Manish Jaggi wrote:
>> I am working on linux 4.2 kernel for our ARM64 platform.
>
> That's lame. I'm working on linux 5.0 kernel for my new arch/zilchcore
> platform.
linux 5.0 kernel ?
--
Albino B Neto
www.bino.us
--
T
On 09/09/15 14:22, Jungseok Lee wrote:
> On Sep 9, 2015, at 1:47 AM, James Morse wrote:
>> On 08/09/15 15:54, Jungseok Lee wrote:
>>> On Sep 7, 2015, at 11:36 PM, James Morse wrote:
diff --git a/arch/arm64/kernel/irq.c b/arch/arm64/kernel/irq.c
index 463fa2e7e34c..10b57a006da8 100644
> -Original Message-
> From: John Youn [mailto:john.y...@synopsys.com]
> Sent: September-03-15 11:53 PM
> To: Scott Branden; John Youn; Greg Kroah-Hartman; linux-
> u...@vger.kernel.org; Roman Bacik
> Cc: linux-kernel@vger.kernel.org; bcm-kernel-feedback-list
> Subject: Re: [PATCH v2 1/1] u
On Wed, 9 Sep 2015 18:27:31 +0800
Chen Yu wrote:
> In current code, max_perf_pct might be smaller than min_perf_pct
> by improper user input:
>
> $ grep . /sys/devices/system/cpu/intel_pstate/m*_perf_pct
> /sys/devices/system/cpu/intel_pstate/max_perf_pct:100
> /sys/devices/system/cpu/intel_pst
On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
> Currently when a uevent occurs, the event is replicated and sent to every
> listener on the kernel netlink socket, ignoring network namespaces boundaries,
> forwarding events to every listener in every network namespace.
>
> With t
The following changes since commit a4fdb2a46f617b8b2cd47acec026ec16532edbc6:
Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2015-09-04 07:18:09
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.
On Tue, Sep 08, 2015 at 10:10:29PM -0400, Michael J. Coss wrote:
> Adds capability to allow userspace programs to forward a given event to
> a specific network namespace as determined by the provided pid. In
> addition, support for a per-namespace kobject_sequence counter was
> added. Sysfs was m
Alexander Stein writes:
> Hi,
> On Tuesday 08 September 2015 18:48:07, Eric Anholt wrote:
>> I finally had a chance to sit down and look at what the hardware's doing
>> with the enable bit (also, I've read a whole lot more of the hardware
>> now, so I'm a lot faster at answering questions like th
On 09.09.2015 6:10, Nicolas Pitre wrote:
On Tue, 8 Sep 2015, Sergey Dyasly wrote:
On 08.09.2015 5:45, Zhang Zhen wrote:
The arch-specific IOREMAP_MAX_ORDER is introduced in
commit: ff0daca([ARM] Add section support to ioremap) and
commit: a069c89 ([ARM] 3705/1: add supersection support to iore
On Wed, Sep 09, 2015 at 10:14:46AM -0300, Emilio López wrote:
> On 09/09/15 01:12, Guenter Roeck wrote:
> >On 09/08/2015 08:58 PM, Greg KH wrote:
> >>On Tue, Sep 08, 2015 at 06:10:16PM -0700, Guenter Roeck wrote:
> >>>Hi Emilio,
> >>>
> >>>On 09/08/2015 05:51 PM, Emilio López wrote:
> Hi Greg &
On 09/04/2015 01:36 PM, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 04, 2015 at 01:20:42PM -0400, Sasha Levin wrote:
>>> Do you have backtrace of this happening? There's a bug in cleanup
>>> path which causes oops (patch is being tested) and this may just be a
>>> symptom of the same problem.
>>
>>
Hi Wolfram,
I have picked this patchset [0] up from Lee to rebase it, with an aim to
get this series moving again.
A couple of minor issues were resolved in the rebase. As it stood, Javier
proposed [1] to merge this series, and use a follow up series to make sure
that all I2C drivers are using a
From: Lee Jones
When there was no other way to match a I2C device to driver i2c_match_id()
was exclusively used. However, now there are other types of tables which
are commonly supplied, matching on an i2c_device_id table is used less
frequently. Instead of _always_ calling i2c_match_id() from
From: Lee Jones
A great deal of I2C devices are currently matched via DT node name, and
as such the compatible naming convention of ',' has gone
somewhat awry - some nodes don't supply one, some supply an arbitrary
string and others the correct device name with an arbitrary vendor prefix.
In an
From: Lee Jones
Also remove unused second probe() parameter 'i2c_device_id'.
Acked-by: Grant Likely
Signed-off-by: Lee Jones
---
drivers/mfd/as3722.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/mfd/as3722.c b/drivers/mfd/as3722.c
index 924ea90..6a
From: Lee Jones
This function provides a single call for all I2C devices which need to
match firstly using traditional OF means i.e by of_node, then if that
fails we attempt to match using the supplied I2C client name with a
list of supplied compatible strings with the ',' string
removed. The la
From: Lee Jones
As part of an effort to rid the mostly unused second parameter for I2C
related .probe() functions and to conform to other existing frameworks
we're moving over to a temporary replacement .probe() call-back.
Acked-by: Grant Likely
Signed-off-by: Lee Jones
---
drivers/mfd/88pm86
From: Lee Jones
This will aid the seamless removal of the current probe()'s, more
commonly unused than used second parameter. Most I2C drivers can
simply switch over to the new interface, others which have DT
support can use its own matching instead and others can call
i2c_match_id() themselves.
From: Lee Jones
Here we're providing dereference protection for i2c_match_id(), which
saves us having to do it each time it's called. We're also stripping
out the (now) needless checks in i2c_device_match(). This patch paves
the way for other, similar code trimming.
Acked-by: Grant Likely
Sig
This initializes drivers (annotated or in the initcall level device)
in parallel.
Which drivers can be initialized in parallel is calculated by using
the dependencies. That means, currently, only annotated drivers which
are are referenced in the used DT will be in order. For all others it
is assum
On Wed, Sep 09 2015, Joe Perches wrote:
> On Wed, 2015-09-09 at 10:38 +0200, Rasmus Villemoes wrote:
>> The double memset is a little ugly; using kzalloc avoids it altogether.
> []
>> diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c
>> b/drivers/net/ethernet/marvell/mv643xx_eth.c
> []
>>
From: Lee Jones
Currently the I2C framework insists on devices supplying an I2C ID
table. Many of the devices which do so unnecessarily adding quite a
few wasted lines to kernel code. This patch allows drivers a means
to 'not' supply the aforementioned table and match on DT match tables
instead
Hello,
as already mentioned, I've implemented the stuff to initialize drivers
in parallel. What follows are two patches to be used on top of my
already posted series (for 4.2) which implements annotated initcalls
and DT based dependencies.
But be warned: many drivers which are in the same initcal
Besides make the code (almost unmeasurable) faster, this makes the
ugly looking loop I've used to remove duplicates cleaner.
Disadvantage is that the ordered array now contains 'holes' and the
number of elements in the array doesn't really match the number
of ordered elements. But this only makes a
On Wed, 2015-09-09 at 20:34 +0200, Rasmus Villemoes wrote:
> mc_spec and mc_other are u32*, we allocate 0x200 = 512 bytes = 128
> u32s, and pointer arithmetic makes mc_other point to the latter 64. Then
> the memory is cleared 256 bytes at a time.
>
> It's unusual and slightly obfuscated code, but
On 09/09/2015 11:23 AM, Kees Cook wrote:
> On Wed, Sep 9, 2015 at 9:56 AM, Shuah Khan wrote:
>> On 09/09/2015 10:45 AM, Shuah Khan wrote:
>>> On 09/09/2015 10:40 AM, Kees Cook wrote:
Re-ping. Can someone pull this into their tree?
-Kees
On Fri, Aug 21, 2015 at 11:22 AM, Ke
On Wed, Sep 09, 2015 at 09:27:04AM +0800, Boqun Feng wrote:
> After commit:
>
> atomics: add acquire/release/relaxed variants of some atomic operations
>
> Architectures may only provide {cmp,}xchg_relaxed definitions in
> asm/cmpxchg.h. Other variants, such as {cmp,}xchg, may be built in
> linux
On Wed, Sep 09 2015, Joe Perches wrote:
> On Wed, 2015-09-09 at 12:13 +0200, Maurizio Lombardi wrote:
>> When printing a bitmap using the "%*pb[l]" printk format
>> a 16 bit variable (field_width) is used to store the size of the bitmap.
>> In some cases 16 bits are not sufficient, the variable o
On Tue, Sep 08, 2015 at 04:35:31PM -0500, Andy Gross wrote:
> This patch adds all the nodes required to support the PM8841 and PM8941
> PMIC regulators present on MSM8974 platforms.
>
> Signed-off-by: Andy Gross
> ---
This patch dupes work done by Bjorn. So I'll take his instead.
--
Qualcomm
Disregard this one. Dupe with different subject line of the other patch 6
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
Jiang Liu wrote on 08/09/15 16:56:
Commit 991de2e59090 ("PCI, x86: Implement pcibios_alloc_irq() and
pcibios_free_irq()") changes the way to allocate PCI legacy IRQ
for PCI devices on x86 platforms. Instead of allocating PCI legacy
IRQs when pcibios_enable_device() gets called, now pcibios_allo
On 9/8/2015 11:54 PM, Greg KH wrote:
> On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
>> Currently when a uevent occurs, the event is replicated and sent to every
>> listener on the kernel netlink socket, ignoring network namespaces
>> boundaries,
>> forwarding events to every li
On Tue, Sep 8, 2015 at 11:49 AM, Jiang Liu wrote:
> Hi Bjorn,
> We have used another draft version to fix this issue by changing
> eata driver as below. But that needs to export pcibios_alloc_irq. And
> I'm not sure whether there are other drivers having the same behavior.
> If we think it
On Wed, Sep 09, 2015 at 02:39:50PM +0200, Petr Mladek wrote:
> On Tue 2015-09-08 12:59:15, Paul E. McKenney wrote:
> > On Mon, Sep 07, 2015 at 04:58:27PM +0200, Petr Mladek wrote:
> > > On Fri 2015-09-04 16:24:22, Paul E. McKenney wrote:
> > > > On Fri, Sep 04, 2015 at 02:11:29PM +0200, Petr Mladek
On 9/8/2015 11:55 PM, Greg KH wrote:
> On Tue, Sep 08, 2015 at 10:10:29PM -0400, Michael J. Coss wrote:
>> Adds capability to allow userspace programs to forward a given event to
>> a specific network namespace as determined by the provided pid. In
>> addition, support for a per-namespace kobject_
- In cqm_pick_event_reader, use the existing package<->core map instead
of looping through all cpus in cqm_cpumask.
- In intel_cqm_cpu_exit, use the same map instead of looping through
all online cpus. In large systems with large number of cpus the time
taken to loop may be expensive and also
There was a push back from cgroup maintainer Tejun on cgroup interface
usage during the previous version of patches. This patch series splits
the prior V13 patches to separate the cqos framework parts which just
provide APis to manage the closid/cbm management, scheduling, hot cpu etc
and the cgrou
Adds some data-structures and APIs to support Class of service
management(closid). There is a new clos_cbm table which keeps a 1:1
mapping between closid and capacity bit mask (cbm)
and a count of usage of closid. Each task would be associated with a
Closid at a time and this patch adds a new field
Adds support for IA32_PQR_ASSOC MSR writes during task scheduling. For
Cache Allocation, MSR write would let the task fill in the cache
'subset' represented by the task's capacity bit mask.
The high 32 bits in the per processor MSR IA32_PQR_ASSOC represents the
CLOSid. During context switch kernel
This patch adds hot cpu support for Intel Cache allocation. Support
includes updating the cache bitmask MSRs IA32_L3_QOS_n when a new CPU
package comes online or goes offline. The IA32_L3_QOS_n MSRs are one per
Class of service on each CPU package. The new package's MSRs are
synchronized with the v
This patch adds different APIs to manage the L3 cache capacity bitmask.
The capacity bit mask(CBM) needs to have only contiguous bits set. The
current implementation has a global CBM for each class of service id.
There are APIs added to update the CBM via MSR write to IA32_L3_MASK_n
on all packages
Adds a description of Cache allocation technology, overview of kernel
framework implementation. The framework has APIs to manage class of
service, capacity bitmask(CBM), scheduling support and other
architecture specific implementation. The APIs are used to build the
cgroup interface in later patch
This patch includes CPUID enumeration routines for Cache allocation and
new values to track resources to the cpuinfo_x86 structure.
Cache allocation provides a way for the Software (OS/VMM) to restrict
cache allocation to a defined 'subset' of cache which may be overlapping
with other 'subsets'. T
Hi,
I've been trying the latest linus/master (a794b4f), which include this
patch, as baremetal kernel on X-gene. This is failing on early boot
without much log.
After bisecting the tree, I found the error coming from this patch.
While this patch is valid, it made me remembered that X-Gene (at lea
On Wed, 2015-09-09 at 20:51 +0200, Rasmus Villemoes wrote:
> On Wed, Sep 09 2015, Joe Perches wrote:
> > this makes the sizeof struct printf_spec more than
> > 8 bytes which isn't desireable on x86-32.
>
> I'm pretty sure struct printf_spec
> purposely has sizeof==8 to allow it to be (relatively
This patch is specific to Intel haswell (hsw) server SKUs. Cache
Allocation on hsw server needs to be enumerated separately as HSW does
not have support for CPUID enumeration for Cache Allocation. This patch
does a probe by writing a CLOSid (Class of service id) into high 32 bits
of IA32_PQR_MSR an
Add documentation on using the cache allocation cgroup interface with
examples.
Signed-off-by: Vikas Shivappa
---
Documentation/cgroups/rdt.txt | 133 ++
1 file changed, 133 insertions(+)
create mode 100644 Documentation/cgroups/rdt.txt
diff --git a/Docu
- In rapl_cpu_init, use the existing package<->core map instead of
looping through all cpus in rapl_cpumask.
- In rapl_cpu_exit, use the same mapping instead of looping all online
cpus. In large systems with large number of cpus the time taken to
loop may be expensive and also the time increa
Adds a new cgroup 'intel_rdt' to manage cache allocation. Each cgroup
directory is associated with a class of service id(closid). To map a
task with closid during scheduling, this patch removes the closid field
from task_struct and uses the already existing 'cgroups' field in
task_struct.
The cgro
On Tue, Sep 08, 2015 at 09:14:01AM +0800, Boqun Feng wrote:
> Two examples for barriers in wake_up() and co. in memory-barriers.txt
> are misleading, along with their explanations:
>
> 1.The example which wanted to explain the write barrier in
> wake_up() and co. [spotted by Oleg Nestero
The syscall ABI is inconsistent on aarch64 compat, so at least we should
document it in the seccomp_bpf tests.
Signed-off-by: Kees Cook
---
Can someone with access to native aarch64 double-check this for me? I
think we need to change these tests to pass if it's expected, but the
compat behavior s
From: Sasha Levin
Date: Tue, 8 Sep 2015 10:53:40 -0400
> There was no verification that an underlying transport exists when creating
> a connection, this would cause dereferencing a NULL ptr.
>
> It might happen on sockets that weren't properly bound before attempting to
> send a message, which
David Drysdale writes:
> On Wed, Sep 9, 2015 at 1:25 AM, Eric W. Biederman
> wrote:
>> Andy Lutomirski writes:
>> > On Tue, Sep 8, 2015 at 4:07 PM, Eric W. Biederman
>> > wrote:
>>
>> >> Perhaps I had missed it but I don't recall capsicum being able to wrap
>> >> things like reboot(2).
>> >>
On Wednesday, September 09, 2015 08:00:20 AM Viresh Kumar wrote:
> On 09-09-15, 03:06, Rafael J. Wysocki wrote:
> > I've just realized that if you combined this patch with the [6/9],
> > you wouldn't need to make any changes to gov_queue_work() at all,
> > because that patch removes the case in poi
301 - 400 of 713 matches
Mail list logo
