On Thu, Nov 30, 2017 at 12:14:47PM +, Colin King wrote:
> From: Colin Ian King
>
> The function update_share_count is local to the source and does
> not need to be in global scope, so make it static.
>
> Cleans up sparse warning:
> fs/btrfs/backref.c:219:6:
On 30/11/17 15:41, Patrick Bellasi wrote:
> On 30-Nov 14:12, Juri Lelli wrote:
> > Hi,
> >
> > On 30/11/17 11:47, Patrick Bellasi wrote:
> >
> > [...]
> >
> > > diff --git a/kernel/sched/cpufreq_schedutil.c
> > > b/kernel/sched/cpufreq_schedutil.c
> > > index 2f52ec0f1539..67339ccb5595 100644
This commit adds a driver for the Virtual Box Guest PCI device used in
Virtual Box virtual machines. Enabling this driver will add support for
Virtual Box Guest integration features such as copy-and-paste, seamless
mode and OpenGL pass-through.
This driver also offers vboxguest IPC functionality
This commit adds the headers describing the ioctl API for the
/dev/vboxguest device used by the Virtual Box Guest Additions
in Virtual Box virtual machines.
The driver providing the /dev/vboxguest device will allow Virtual Box
Guest Additions features such as copy-and-paste, seamless mode and
On 30-Nov 14:41, Juri Lelli wrote:
> Hi,
>
> On 30/11/17 11:47, Patrick Bellasi wrote:
> > In system where multiple CPUs shares the same frequency domain a small
> > workload on a CPU can still be subject to frequency spikes, generated by
> > the activation of the sugov's kthread.
> >
> > Since
On 11/30/17 6:43 AM, Roman Gushchin wrote:
> @@ -75,12 +80,13 @@ static int do_help(int argc, char **argv)
> fprintf(stderr,
> "Usage: %s [OPTIONS] OBJECT { COMMAND | help }\n"
> " %s batch file FILE\n"
> + " %s cgattach FILE CGROUP TYPE\n"
On Thu, 30 Nov 2017 16:41:08 +0100
Sebastian Andrzej Siewior wrote:
> I would keep it for now until we decide if we keep fixing those things
> are disable for RT because it is not worth it. As I said, this is only
> x86 specific and we have something similar on ARM with
On Thu, Nov 30, 2017 at 07:51:17AM -0800, Dave Hansen wrote:
> On 11/30/2017 07:44 AM, Peter Zijlstra wrote:
> > On Mon, Nov 27, 2017 at 11:49:14AM +0100, Ingo Molnar wrote:
> >> @@ -338,24 +366,23 @@ static inline void
> >> __native_flush_tlb_single(unsigned long addr)
> >>
> >> static inline
This patch brings no functional changes.
It moves out the VLAN code iterating on a list of VLAN members into new
dsa_switch_vlan_{prepare,add}_bitmap() functions.
This gives us a better isolation of the two switchdev phases.
Signed-off-by: Vivien Didelot
---
The DSA switch VLAN ops pass the switchdev_trans structure down to the
drivers, but no one is using them and they aren't supposed to anyway.
Remove the trans argument from VLAN prepare and add operations.
At the same time, fix the following checkpatch warning:
WARNING: line over 80
On Thu, Nov 30, 2017 at 08:14:01AM -0800, Paul E. McKenney wrote:
> > (Also, technically speaking, the litmus test doesn't have any release
> > operations, so no release sequence...)
>
> True! But if you translated it into C11, you would probably turn the
> smp_wmb() followed by write into a
This patch series brings no functional changes.
It removes the unused switchdev_trans arguments from the dsa_switch_ops
for both MDB and VLAN operations, and provides functions to prepare and
add these objects for a given bitmap of ports.
Vivien Didelot (4):
net: dsa: remove trans argument
On Thu, Nov 30, 2017 at 09:56:08AM -0600, Andrew F. Davis wrote:
> On 11/30/2017 06:20 AM, Mark Brown wrote:
> > disable them. Based on what I think the intention is I'd suggest
> > removing the bias level handling and then having probe enable runtime
> > PM with the device flagged as active,
We rely on an atomic swizzling of TTBR1 when transitioning from the entry
trampoline to the kernel proper on an exception. We can't rely on this
atomicity in the face of Falkor erratum #E1003, so on affected cores we
can issue a TLB invalidation to invalidate the walk cache prior to
jumping into
Hi again,
This is version two of the patches previously posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
Changes since v1 include:
* Based on v4.15-rc1
* Trampoline moved into FIXMAP area
* Explicit static key replaced by cpu cap
* Disable
We're about to rework the way ASIDs are allocated, switch_mm is
implemented and low-level kernel entry/exit is handled, so keep the
ARM64_SW_TTBR0_PAN code out of the way whilst we do the heavy lifting.
It will be re-enabled in a subsequent patch.
Signed-off-by: Will Deacon
Memory entry could be allocated in different ways (ioremap,
dma_alloc_coherent, internal RAM allocator...).
This patch introduces a release ops in rproc_mem_entry structure
to associate dedicated release mechanism to each memory entry descriptor
in order to keep remoteproc core generic.
In preparation for separate kernel/user ASIDs, allocate them in pairs
for each mm_struct. The bottom bit distinguishes the two: if it is set,
then the ASID will map only userspace.
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/mmu.h | 1 +
arch/arm64/mm/context.c
On Fri, Dec 1, 2017 at 12:41 AM, Jiri Kosina wrote:
> On Fri, 1 Dec 2017, Yu Chen wrote:
>
>> BTW, is nfs able to be included in this set? I also encountered a
>> freeze() failure due to nfs access during that stage recently.
>
> The freezer usage in NFS is magnitudes more
Hi Will,
On 30/11/17 16:39, Will Deacon wrote:
We rely on an atomic swizzling of TTBR1 when transitioning from the entry
trampoline to the kernel proper on an exception. We can't rely on this
atomicity in the face of Falkor erratum #E1003, so on affected cores we
can issue a TLB invalidation to
Same here. It's "Move" not "Mov" ;-)
I made the modification while pulling in the patch.
-- Steve
On Wed 29-11-17 15:23:48, Luis R. Rodriguez wrote:
> The question of whether or not a superblock is frozen needs to be
> augmented in the future to account for differences between a user
> initiated freeze and a kernel initiated freeze done automatically
> on behalf of the kernel.
>
> Provide
From: Srinivas Kandagatla
This patch adds support to read/write SLIMbus value elements.
Currently it only supports byte read/write. Adding this support in
regmap would give codec drivers more flexibility when there are more
than 2 control interfaces like SLIMbus,
From: Srinivas Kandagatla
This patch adds support to parse slim devices from device tree.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/core.c | 50 ++
1 file changed, 50
From: Sagar Dharia
This patch add device tree bindings for Qualcomm slimbus controller.
Signed-off-by: Sagar Dharia
Signed-off-by: Srinivas Kandagatla
---
.../devicetree/bindings/slimbus/slim-qcom-ctrl.txt | 39
From: Srinivas Kandagatla
This patch adds some common constant defines which are required
for qcom slim controller driver.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/slimbus.h | 33 +
1
From: Srinivas Kandagatla
Add myself as maintainer for slimbus.
Signed-off-by: Srinivas Kandagatla
Acked-by: Bjorn Andersson
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git
Utilize the much more capable b53_get_tag_protocol() which takes care of
all Broadcom switches specifics to resolve which port can have Broadcom
tags enabled or not.
Signed-off-by: Florian Fainelli
---
drivers/net/dsa/b53/b53_common.c | 4 ++--
On Thu, 2017-11-30 at 12:31 -0500, David Miller wrote:
> From: Joe Perches
> Date: Thu, 30 Nov 2017 08:21:14 -0800
>
> > When enabled, the current debug logging does not have a KERN_.
> > Add KERN_DEBUG to the logging macros.
> >
> > Miscellanea:
> >
> > o Remove #define
Implementation of the unpinned APIC page didn't update the VMCS address
cache when invalidation was done through range mmu notifiers.
This became a problem when the page notifier was removed.
Re-introduce the arch-specific helper and call it from ...range_start.
Fixes: 38b9917350cb ("kvm: vmx:
Does roughly what kvm_mmu_notifier_invalidate_page did before.
I am not certain why this would be needed. It might mean that we have
another bug with start/end or just that I missed something.
Please try just [1/2] first and apply this one only if [1/2] still bugs,
thanks!
---
On 11/30/2017 06:20 AM, Mark Brown wrote:
> On Wed, Nov 29, 2017 at 12:50:15PM -0600, Andrew F. Davis wrote:
>
>> +case SND_SOC_BIAS_STANDBY:
>> +pcm186x_power_on(codec);
>> +break;
>> +case SND_SOC_BIAS_OFF:
>> +pcm186x_power_off(codec);
>> +
On Thu, Nov 30, 2017 at 08:18:26AM -0800, Tony Lindgren wrote:
> So it seems this and patch 8/8 are safe for me to pick separately?
It might make sense to pull in the relevant branches from ASoC first
however IIRC the reset GPIO code currently does nothing useful anyway so
it won't have any
On 11/30/2017 12:50 AM, Paul Lawrence wrote:
> Use cc-option to figure out whether the compiler's sanitizer uses
> LLVM-style parameters ("-mllvm -asan-foo=bar") or GCC-style parameters
> ("--param asan-foo=bar").
>
> Signed-off-by: Greg Hackmann
> Signed-off-by: Paul
In preparation for mapping kernelspace and userspace with different
ASIDs, move the ASID to TTBR1 and update switch_mm to context-switch
TTBR0 via an invalid mapping (the zero page).
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/mmu_context.h | 7 +++
The pre_ttbr0_update_workaround hook is called prior to context-switching
TTBR0 because Falkor erratum E1003 can cause TLB allocation with the wrong
ASID if both the ASID and the base address of the TTBR are updated at
the same time.
With the ASID sitting safely in TTBR1, we no longer update
Hi Greg,
On Thursday 30 November 2017 10:11 PM, Greg KH wrote:
On Thu, Nov 30, 2017 at 09:13:35PM +0530, Arvind Yadav wrote:
platform_get_irq() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
On 30/11/17 16:19, Patrick Bellasi wrote:
> On 30-Nov 17:02, Juri Lelli wrote:
> > On 30/11/17 15:41, Patrick Bellasi wrote:
> > > On 30-Nov 14:12, Juri Lelli wrote:
> > > > Hi,
> > > >
> > > > On 30/11/17 11:47, Patrick Bellasi wrote:
> > > >
> > > > [...]
> > > >
> > > > > diff --git
On Thu, Nov 30, 2017 at 09:17:17AM -0700, David Ahern wrote:
> On 11/30/17 6:43 AM, Roman Gushchin wrote:
> > @@ -75,12 +80,13 @@ static int do_help(int argc, char **argv)
> > fprintf(stderr,
> > "Usage: %s [OPTIONS] OBJECT { COMMAND | help }\n"
> > " %s batch
With the ASID now installed in TTBR1, we can re-enable ARM64_SW_TTBR0_PAN
by ensuring that we switch to a reserved ASID of zero when disabling
user access and restore the active user ASID on the uaccess enable path.
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig
The post_ttbr0_update_workaround hook applies to any change to TTBRx_EL1.
Since we're using TTBR1 for the ASID, rename the hook to make it clearer
as to what it's doing.
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/assembler.h | 5 ++---
arch/arm64/kernel/entry.S
On Thu, Nov 30, 2017 at 04:41:05PM +, Will Deacon wrote:
> On Thu, Nov 30, 2017 at 08:14:01AM -0800, Paul E. McKenney wrote:
> > On Thu, Nov 30, 2017 at 10:20:02AM -0500, Alan Stern wrote:
> > > On Wed, 29 Nov 2017, Daniel Lustig wrote:
> > >
> > > > On 11/29/2017 12:42 PM, Paul E. McKenney
On 11/29/2017 5:16 PM, Bjorn Andersson wrote:
Add the helper library for encoding and decoding QMI encoded messages.
The implementation is taken from lib/qmi_encdec.c of the Qualcomm kernel
(msm-3.18).
Modifications has been made to the public API, source buffers has been
made const and the
On Thu, Nov 30, 2017 at 03:27:02PM +0530, Vinod Koul wrote:
> +EXPORT_SYMBOL_GPL(__regmap_init_sdw);
Thanks for fixing this, this looks good now. We'll need to work out how
this winds up getting merged in whenever that happens.
signature.asc
Description: PGP signature
On Wed, Nov 29, 2017 at 07:35:31PM -0500, Theodore Ts'o wrote:
> On Wed, Nov 29, 2017 at 11:28:52AM -0600, Serge E. Hallyn wrote:
> >
> > Just to be clear, module loading requires - and must always continue to
> > require - CAP_SYS_MODULE against the initial user namespace. Containers
> > in
On 30/11/2017 at 09:16:38 -0800, Guenter Roeck wrote:
> On Wed, Nov 29, 2017 at 09:56:29PM +0100, Alexandre Belloni wrote:
> > On 29/11/2017 at 12:53:11 -0800, Guenter Roeck wrote:
> > > On Mon, Nov 27, 2017 at 05:31:01PM +0100, Peter Rosin wrote:
> > > > The I2C adapter driver is sometimes slow,
On 11/30/2017 12:23 PM, David Sterba wrote:
On Wed, Nov 29, 2017 at 01:38:26PM -0500, Chris Mason wrote:
On 11/29/2017 12:05 PM, Tejun Heo wrote:
On Wed, Nov 29, 2017 at 09:03:30AM -0800, Tejun Heo wrote:
Hello,
On Wed, Nov 29, 2017 at 05:56:08PM +0100, Jan Kara wrote:
What has happened
On Thu, Nov 30, 2017 at 09:21:49PM +0900, Masahiro Yamada wrote:
> BTW, did this patch work in your test?
Yes, but it looks like /bin/sh is symlinked to bash on my system. I can
reproduce the issue with dash.
> As for the macro names, maybe
>
> __cc-ifversion, __cc-if-fullversion for
On Wed, Nov 29, 2017 at 04:32:52PM -0800, Nick Desaulniers wrote:
> Right, but you're still only ever using one linker per build, correct?
Correct. LDFLAGS_GOLD makes it move convenient to add gold specific flags
without explicit $(ld-name) checks everywhere, but I'm fine with removing
it in v2.
From: Sagar Dharia
This controller driver programs manager, interface, and framer
devices for Qualcomm's slimbus HW block.
Manager component currently implements logical address setting,
and messaging interface.
Interface device reports bus synchronization information,
From: Sagar Dharia
Per SLIMbus specification, a reconfiguration sequence known as
'clock pause' needs to be broadcast over the bus while entering low-
power mode. Clock-pause is initiated by the controller driver.
To exit clock-pause, controller typically wakes up the
From: Sagar Dharia
Slimbus HW mandates that clock-pause sequence has to be executed
before disabling relevant interface and core clocks.
Runtime-PM's autosuspend feature is used here to enter/exit low
power mode for Qualcomm's Slimbus controller. Autosuspend feature
On 11/29/2017 12:21 AM, Alexey Brodkin wrote:
As of today we assumed that "machine_desc->init_per_cpu" calls
are only usable on SMP systems when we want to run some piece of
code on early boot for each and every core, I guess assumption was
we have "machine_desc->init_early" for single-core
Add a new helper returning the local port used to reach an arbitrary
switch port in the fabric.
Its only user at the moment is the dsa_upstream_port helper, which
returns the local port reaching the dedicated CPU port, but it will be
used in cross-chip FDB operations.
Signed-off-by: Vivien
On 11/30/2017 07:44 AM, Peter Zijlstra wrote:
> On Mon, Nov 27, 2017 at 11:49:14AM +0100, Ingo Molnar wrote:
>> @@ -338,24 +366,23 @@ static inline void __native_flush_tlb_single(unsigned
>> long addr)
>>
>> static inline void __flush_tlb_all(void)
>> {
>> +if
This commits adds a header describing the hardware interface for the
Virtual Box Guest PCI device used in Virtual Box virtual machines and
utility functions for talking to the Virtual Box hypervisor over this
interface.
These utility functions will used both by the vboxguest driver for the
PCI
Hi,
On 29-11-17 18:10, Philippe Ombredanne wrote:
On Wed, Nov 29, 2017 at 4:55 PM, Hans de Goede wrote:
diff --git a/drivers/virt/vboxguest/vboxguest_core.c
b/drivers/virt/vboxguest/vboxguest_core.c
new file mode 100644
index ..631101578c2a
--- /dev/null
+++
On 30/11/2017 13:04, Colin King wrote:
> From: Colin Ian King
>
> The array audit_point_name is local to the source and does not need to
> be in global scope, so make it static.
>
> Cleans up sparse warning:
> arch/x86/kvm/mmu_audit.c:22:12: warning: symbol
This patch brings no functional changes.
It moves out the MDB code iterating on a multicast group into new
dsa_switch_mdb_{prepare,add}_bitmap() functions.
This gives us a better isolation of the two switchdev phases.
Signed-off-by: Vivien Didelot
---
The DSA switch MDB ops pass the switchdev_trans structure down to the
drivers, but no one is using them and they aren't supposed to anyway.
Remove the trans argument from MDB prepare and add operations.
Signed-off-by: Vivien Didelot
---
On Wed, Nov 29, 2017 at 01:36:25PM -0800, Linus Torvalds wrote:
> On Wed, Nov 29, 2017 at 1:14 PM, Linus Torvalds
> wrote:
> >
> > Not because %pK itself changed, but because the semantics of %p did.
> > The baseline moved, and the "safe" version did not.
>
> Btw,
When running with the kernel unmapped whilst at EL0, the virtually-addressed
SPE buffer is also unmapped, which can lead to buffer faults if userspace
profiling is enabled.
This patch prohibits SPE profiling of userspace when
arm_kernel_unmapped_at_el0().
Signed-off-by: Will Deacon
We will need to treat exceptions from EL0 differently in kernel_ventry,
so rework the macro to take the exception level as an argument and
construct the branch target using that.
Signed-off-by: Will Deacon
---
arch/arm64/kernel/entry.S | 46
On 30-Nov 17:12, Juri Lelli wrote:
> On 30/11/17 16:02, Patrick Bellasi wrote:
> > On 30-Nov 14:41, Juri Lelli wrote:
>
> [...]
>
> > > If the DL changes (which I shall post again as soon as tip/sched/core is
> > > bumped up to 4.15-rc1) get in first, this is going to be useless (as the
> > > DL
Allow explicit disabling of the entry trampoline on the kernel command
line (kaiser=off) by adding a fake CPU feature (ARM64_UNMAP_KERNEL_AT_EL0)
that can be used to toggle the alternative sequences in our entry code and
avoid use of the trampoline altogether if desired. This also allows us to
Look-up for a pre-registred carveout having the same
name as requested one.
If match found, pre-registed carevout is used and resource
table updated.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 17 -
1 file changed, 16
Add the possibility to associate a memory device to
carveout.
Due to some memory mapping constraints, remoteproc related memory
allocations should be done in a specific memory region.
Constraint is not coming from remoteproc firmware (with defined
device address), but from remoteproc platform
Enable memory device creation for each memory region added
by rproc_add_carveout function.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/st_remoteproc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/remoteproc/st_remoteproc.c
This patch parse existing carveout list to find a memory area
matching on "vdevbuffer" name.
If found, memory device will be used as parent for vdev creation, else
rproc platform device will be used as today.
Signed-off-by: Loic Pallardy
---
This patch parse existing carveout list to find a memory area
matching on name.
Naming rule for search is the following one:
- "vdevvring" to find a memory pool dedicated to
one vring belonging to one specific vdev (vdev_id).
- "vdevvrings> to find common memory pool for allocation of
all vrings
Em Mon, Nov 27, 2017 at 09:20:05PM -0600, Kim Phillips escreveu:
> On Sun, 26 Nov 2017 20:20:58 -0800
> Davidlohr Bueso wrote:
>
> > I'm resending the patches from James Yang and Kim Phillips that
> > improve the perf bench futex benchmarks. Noticibly:
>
> Thanks!
> > patch1
On Wed 29-11-17 15:23:47, Luis R. Rodriguez wrote:
> thaw_super() hold a write lock, however we wish to also enable
> callers which already hold the write lock. To do this provide a helper
> and make thaw_super() use it. This way, all that thaw_super() does
> now is lock handling and active count
ndy Dunlap <rdun...@infradead.org>
---
drivers/staging/ipx/Kconfig |1 +
1 file changed, 1 insertion(+)
--- linux-next-20171130.orig/drivers/staging/ipx/Kconfig
+++ linux-next-20171130/drivers/staging/ipx/Kconfig
@@ -3,6 +3,7 @@
#
config IPX
tristate "The IPX protocol"
+ d
On Wed, Nov 29, 2017 at 5:58 PM, Nicholas Piggin wrote:
> (Comparing `readelf -S` before/after is a way to spot bugs.)
Do you have a script that can be used to diff 2 `readelf -S`, look for
missing references, and report an error? Might be easier to rerun that
every so often
On 11/27/2017 08:51 AM, Bjorn Helgaas wrote:
FYI. This was reported against drivers/pci, but it doesn't look like
a PCI core issue to me.
Not a PCI issue, it was a change I did. To whom shall I send the patch
for testing?
This change was in linux-next for many months, and I don't have
On 30 November 2017 at 17:10, Greg Kroah-Hartman
wrote:
> On Thu, Nov 30, 2017 at 04:32:35PM +, Greg Kroah-Hartman wrote:
>> On Wed, Nov 29, 2017 at 01:36:25PM -0800, Linus Torvalds wrote:
>> > On Wed, Nov 29, 2017 at 1:14 PM, Linus Torvalds
>> >
On Wed, Nov 29, 2017 at 01:38:26PM -0500, Chris Mason wrote:
> On 11/29/2017 12:05 PM, Tejun Heo wrote:
> > On Wed, Nov 29, 2017 at 09:03:30AM -0800, Tejun Heo wrote:
> >> Hello,
> >>
> >> On Wed, Nov 29, 2017 at 05:56:08PM +0100, Jan Kara wrote:
> >>> What has happened with this patch set?
> >>
>
Hi Dave,
Because unavailable memory can be in the middle of a section, I think
a proper fix would be to do pfn_valid() check only at the beginning of
section. Otherwise, we might miss zeroing a struct page is in the
middle of a section but pfn_valid() could potentially return false as
that page
Hi Archit,
On 2017年10月26日 12:53, Archit Taneja wrote:
On 10/25/2017 09:21 AM, Nickey Yang wrote:
Configure dsi slave channel when driving a panel
which needs 2 DSI links.
Signed-off-by: Nickey Yang
---
On 11/29/2017 5:16 PM, Bjorn Andersson wrote:
Drivers that needs to communicate with a remote QMI service all has to
perform the operations of discovering the service, encoding and decoding
the messages and operate the socket. This introduces an abstraction for
these common operations,
On 11/29/2017 5:16 PM, Bjorn Andersson wrote:
Introduce a sample driver that register for server notifications and
spawn clients for each available test service (service 15). The spawned
clients implements the interface for encoding "ping" and "data" requests
and decode the responses from the
About 40 of the approximately 180 users of the IDR in the kernel are
"1-based" instead of "0-based". That is, they never want to have ID 0
allocated; they want to see IDs allocated between 1 and N. Usually, that's
expressed like this:
/* Get the user-visible handle using idr. */
On Sat, Nov 25, 2017 at 09:29:24PM +0200, Jarkko Sakkinen wrote:
> +static void *sgx_try_alloc_page(void)
> +{
> + struct sgx_epc_bank *bank;
> + void *page = NULL;
> + int i;
> +
> + for (i = 0; i < sgx_nr_epc_banks; i++) {
> + bank = _epc_banks[i];
> +
> +
On 29 November 2017 at 09:02, James Morse wrote:
> Hi Mathieu,
>
> On 21/11/17 19:06, Mathieu Poirier wrote:
>> On 21 November 2017 at 09:47, James Morse wrote:
>>> On 18/11/17 09:12, Leo Yan wrote:
The upper patch has no issue if enabled crash dump
Hi Sergey,
On Tue, Nov 28, 2017 at 11:25 PM, Sergey Senozhatsky
wrote:
> On (11/28/17 16:13), Kevin Hilman wrote:
> [..]
>> > okay... who's going to send the patch? kernelCI folks?
>> >
>> > I have some sort of a patch. added console_msg_format= with the only
Hi Vincent,
On Mon, Nov 20 2017 at 09:04, Vincent Guittot wrote:
> On 24 October 2017 at 14:25, Brendan Jackman wrote:
>> @@ -9062,7 +9109,12 @@ static __latent_entropy void
>> run_rebalance_domains(struct softirq_action *h)
>> * and abort nohz_idle_balance
On Thu, Nov 30, 2017 at 3:29 PM, Adrian Hunter wrote:
> On 29/11/17 01:03, Atul Garg wrote:
[]
>> diff --git a/drivers/mmc/host/sdhci-pci-arasan.c
>> b/drivers/mmc/host/sdhci-pci-arasan.c
>> new file mode 100644
>> index 000..6529f30
>> --- /dev/null
>> +++
When enabled, the current debug logging does not have a KERN_.
Add KERN_DEBUG to the logging macros.
Miscellanea:
o Remove #define redundancy and neaten the macros a bit
Signed-off-by: Joe Perches
---
net/rxrpc/ar-internal.h | 75
On Wed 29-11-17 15:23:52, Luis R. Rodriguez wrote:
> This removes superflous freezer calls as they are no longer needed
> as the VFS now performs filesystem freezing/thaw if the filesystem has
> support for it.
>
> The following Coccinelle rule was used as follows:
>
> spatch --sp-file
Replying to Salvatore and Ian at once, and CC'ing H. Peter Anvin and
Karel Zak for util-linux flock(1).
On Thu, Nov 30, 2017 at 02:57:06PM +, Ian Campbell wrote:
> On Thu, 2017-11-30 at 15:39 +0100, Salvatore Mesoraca wrote:
> > 2017-11-27 1:26 GMT+01:00 Solar Designer :
>
In preparation for unmapping the kernel whilst running in userspace,
make the kernel mappings non-global so we can avoid expensive TLB
invalidation on kernel exit to userspace.
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/kernel-pgtable.h | 12 ++--
On Thu, Nov 30, 2017 at 1:53 AM, Michal Hocko wrote:
> On Wed 29-11-17 10:05:35, Dan Williams wrote:
>> Until there is a solution to the dma-to-dax vs truncate problem it is
>> not safe to allow long standing memory registrations against
>> filesytem-dax vmas. Device-dax vmas
On Wed, Nov 29, 2017 at 07:24:48PM +0100, Javier Martinez Canillas wrote:
> Hello Jarkko,
>
> On 11/29/2017 06:57 PM, Jarkko Sakkinen wrote:
> > On Wed, Nov 29, 2017 at 12:08:46PM +0100, Javier Martinez Canillas
> > wrote:
> >> +#define TPM2_RC_LAYER_SHIFT 16 +#define
On Thu, Nov 30, 2017 at 05:25:01PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 30, 2017 at 08:14:01AM -0800, Paul E. McKenney wrote:
> > > (Also, technically speaking, the litmus test doesn't have any release
> > > operations, so no release sequence...)
> >
> > True! But if you translated it
On 11/30/2017 7:12 AM, Johannes Thumshirn wrote:
One major usability difference between NVMf RDMA and FC is resolving
the default host transport address in RDMA. This is perfectly doable
in FC as well, as we already have all possible lport <-> rport
combinations pre-populated so we can pick the
The exception entry trampoline needs to be mapped at the same virtual
address in both the trampoline page table (which maps nothing else)
and also the kernel page table, so that we can swizzle TTBR1_EL1 on
exceptions from and return to EL0.
This patch maps the trampoline at a fixed virtual
On Thu, Nov 30, 2017 at 04:05:45PM +1300, Kai Huang wrote:
> On Wed, 2017-11-29 at 17:38 +0200, Jarkko Sakkinen wrote:
> > On Wed, Nov 29, 2017 at 12:21:41AM +0200, Jarkko Sakkinen wrote:
> > > On Tue, Nov 28, 2017 at 02:00:03PM -0800, Sean Christopherson
> > > wrote:
> > > > What about
Hook up the entry trampoline to our exception vectors so that all
exceptions from and returns to EL0 go via the trampoline, which swizzles
the vector base register accordingly. Transitioning to and from the
kernel clobbers x30, so we use tpidrro_el0 and far_el1 as scratch
registers for native
On Thu, Nov 30, 2017 at 10:37:22AM -0600, Andrew F. Davis wrote:
> On 11/30/2017 10:33 AM, Mark Brown wrote:
> > It might make sense to pull in the relevant branches from ASoC first
> > however IIRC the reset GPIO code currently does nothing useful anyway so
> > it won't have any impact on
From: Salvatore Mesoraca
> Sent: 22 November 2017 08:02
>
> Disallows O_CREAT open missing the O_EXCL flag, in world or
> group writable directories, even if the file doesn't exist yet.
> With few exceptions (e.g. shared lock files based on flock())
> if a program tries to open a file, in a
1 - 100 of 2288 matches
Mail list logo