On Thursday 25 June 2015 11:20 AM, Krzysztof Kozlowski wrote:
On 25.06.2015 14:44, Vaibhav Hiremath wrote:
On Thursday 25 June 2015 11:02 AM, Krzysztof Kozlowski wrote:
On 25.06.2015 14:26, Vaibhav Hiremath wrote:
On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
2015-06-24
On 25.06.2015 14:44, Vaibhav Hiremath wrote:
>
>
> On Thursday 25 June 2015 11:02 AM, Krzysztof Kozlowski wrote:
>> On 25.06.2015 14:26, Vaibhav Hiremath wrote:
>>>
>>>
>>> On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
:
>
On Thu, Jun 25, 2015 at 05:33:34AM +0100, Al Viro wrote:
> On Wed, Jun 24, 2015 at 08:42:02PM -0700, Linus Torvalds wrote:
> > On Wed, Jun 24, 2015 at 1:25 PM, Jaegeuk Kim wrote:
> > >
> > > New features are:
> > > o per-file encryption (e.g., ext4)
> >
> > The new encrypted symlinks needed
On Tue, 2015-06-23 at 00:25 +0200, Marcus Gelderie wrote:
> A while back, the message queue implementation in the kernel was
> improved to use btrees to speed up retrieval of messages (commit
> d6629859b36). The patch introducing the improved kernel handling of
> message queues (using btrees) has,
On Thursday 25 June 2015 10:08 AM, Tony Lindgren wrote:
* Vaibhav Hiremath [150624 10:12]:
I do not like this, as this is not HW feature, so DT may not be right
approach.
So I will dig more from either runtime or Compile time option to use
regmap_ Vs raw read/writes.
Can't you just check
On Thursday 25 June 2015 11:02 AM, Krzysztof Kozlowski wrote:
On 25.06.2015 14:26, Vaibhav Hiremath wrote:
On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
:
As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
(page 0) controls
On 25.06.2015 14:27, Vaibhav Hiremath wrote:
>
>
> On Thursday 25 June 2015 05:27 AM, Krzysztof Kozlowski wrote:
>> 2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
>> :
>>> Add DT support to the 88pm800 driver, along with compatible
>>> field for it's sub-devices (rtc, onkey and regulator)
>>>
>>>
On 25.06.2015 14:26, Vaibhav Hiremath wrote:
>
>
> On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
>> 2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
>> :
>>> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
>>> (page 0) controls the method of clearing interrupt
>>> status of
Hi Florian,
On Wed, Jun 24, 2015 at 09:48:46PM -0700, Florian Fainelli wrote:
> Hi,
>
> Could you backport this commit:
> 72cf90124e87d975d0b2114d930808c58b4c05e4 ("lzo: check for length overrun
> in variable length encoding.") into stable kernels older than 3.18?
>
> It should apply cleanly to
On Thursday 25 June 2015 05:27 AM, Krzysztof Kozlowski wrote:
2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath :
Add DT support to the 88pm800 driver, along with compatible
field for it's sub-devices (rtc, onkey and regulator)
Signed-off-by: Chao Xie
Signed-off-by: Vaibhav Hiremath
---
On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath :
As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
(page 0) controls the method of clearing interrupt
status of 88pm800 family of devices;
0: clear on read
1: clear on write
Hello Johan,
Peter Hung 於 2015/6/15 上午 09:54 寫道:
> This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
>
> Features:
> 1. F81534 is 1-to-4 & F81532 is 1-to-2 serial ports IC
> 2. Support Baudrate from B50 to B150 (excluding B100).
> 3. The RTS signal can be transformed their
* Arnd Bergmann [150515 13:23]:
> On Friday 15 May 2015 22:16:24 Pali Rohár wrote:
> > On Friday 15 May 2015 22:12:41 Arnd Bergmann wrote:
> > > On Friday 15 May 2015 21:50:07 Pali Rohár wrote:
> > > > }
> > > >
> > > > }
> > > >
> > > > + /* include the
* Arnd Bergmann [150515 13:11]:
> On Friday 15 May 2015 21:50:06 Pali Rohár wrote:
> > @@ -256,5 +257,10 @@ const struct machine_desc * __init
> > setup_machine_fdt(unsigned int dt_phys)
> > system_rev = 0;
> > }
> >
> > + /* Save atags */
> > + prop
* Pali Rohár [150506 04:45]:
> On Wednesday 06 May 2015 13:04:01 Arnd Bergmann wrote:
> > >
> > > It needs to be done in this code, so "system_rev" variable is set
> > > properly...
> >
> > What I mean is which code accesses this variable that early?
> >
>
> ATAG code is doing it at same
Hi Linus,
Here's my suggested merge resolution to deal with Al Viro's symlink changes.
- Ted
diff --cc fs/ext4/symlink.c
index ba5bd18,68e915a..000
--- a/fs/ext4/symlink.c
+++ b/fs/ext4/symlink.c
@@@ -35,19 -34,20 +34,17 @@@ static const char
Header is not needed for arm/hw_breakpoint.c,
Removing the same.
Signed-off-by: Maninder Singh
Reviewed-by: Vaneet Narang
---
arch/arm/kernel/hw_breakpoint.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/arm/kernel/hw_breakpoint.c
Hi,
Could you backport this commit:
72cf90124e87d975d0b2114d930808c58b4c05e4 ("lzo: check for length overrun
in variable length encoding.") into stable kernels older than 3.18?
It should apply cleanly to anything that contains
8b975bd3f9089f8ee5d7bbfd798537b992bbc7e7 ("lib/lzo: Update LZO
On Wed, Jun 24, 2015 at 11:22:24PM +0530, Santosh wrote:
> try_module_get fails when the reference count of the module is not
> allowed to be incremented ,and hence -ENXIO is returned indicating
> no device or address.
1) this patch is 2/2, but then where is your 1/2 patch?
2) You have used
* Vaibhav Hiremath [150624 10:12]:
>
> I do not like this, as this is not HW feature, so DT may not be right
> approach.
>
> So I will dig more from either runtime or Compile time option to use
> regmap_ Vs raw read/writes.
Can't you just check if the pinctrl node has compatible = "syscon"
On Wed, Jun 24, 2015 at 12:12:01PM +0200, Luis de Bethencourt wrote:
> On Wed, Jun 24, 2015 at 11:05:16AM +0530, Sudip Mukherjee wrote:
> > On Tue, Jun 23, 2015 at 03:10:56PM +0200, Luis de Bethencourt wrote:
>
> I based the patch on staging's master and not on the staging-next branch.
use
On Thu, 25 Jun 2015 00:03:02 -0400
Sasha Levin wrote:
> On 06/17/2015 08:36 AM, Steven Rostedt wrote:
> > Linus,
> >
> > Vince Weaver reported a warning when he added perf event filters
> > into his fuzzer tests. There's a missing check of balanced
> > operations when parenthesis are used, and
On Wed, Jun 24, 2015 at 08:42:02PM -0700, Linus Torvalds wrote:
> On Wed, Jun 24, 2015 at 1:25 PM, Jaegeuk Kim wrote:
> >
> > New features are:
> > o per-file encryption (e.g., ext4)
>
> The new encrypted symlinks needed fixups for the changes that happened
> meanwhile to the symlink handling.
On Wed, Jun 24, 2015 at 10:57:51AM +0800, Alex Hung wrote:
> ASUS introduced a new approach to handle wireless hotkey
> since Windows 8. When the hotkey is pressed, BIOS generates
> a notification 0x88 to a new ACPI device, ATK4001. This
> new driver not only translates the notification to
On 06/17/2015 08:36 AM, Steven Rostedt wrote:
> Linus,
>
> Vince Weaver reported a warning when he added perf event filters
> into his fuzzer tests. There's a missing check of balanced
> operations when parenthesis are used, and this triggers a WARN_ON()
> and when reading the failure, the filter
CONFIG_GIANFAR is not depended on FSL_SOC, it
can be built on non-PPC platforms.
Signed-off-by: Alison Wang
---
drivers/net/ethernet/freescale/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/freescale/Kconfig
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus
for you to fetch changes up to
On Wed, Jun 24, 2015 at 1:25 PM, Jaegeuk Kim wrote:
>
> New features are:
> o per-file encryption (e.g., ext4)
The new encrypted symlinks needed fixups for the changes that happened
meanwhile to the symlink handling. I did all that in my merge, and I
*think* I got it all right, but I would like
On Thu, 21 May 2015 13:30:08 -0400
Josef Bacik wrote:
> +static void merge_tasks(struct handle_data *h)
> +{
> + struct trace_hash_item **bucket;
> + struct trace_hash_item *item;
> +
> + if (!merge_like_comms)
> + return;
> +
> + trace_hash_for_each_bucket(bucket,
On 06/24/2015 05:03 PM, Dave Hansen wrote:
> In any case, we ratelimit might_sleep() checks anyway. But, we
> do the ratelimiting *after* we check the other conditions for
> might_sleep() including the (costly) irqs_disabled() call.
Thinking about this a bit more, this patch is wrong.
This only
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
> On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
> wrote:
>> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
>>> 4.2 material I suppose?
>>
>> And stable. Without this, if you configure without TICK_ONESHOT, the
>> machine
On Thu, 21 May 2015 13:30:08 -0400
Josef Bacik wrote:
> +static int compare_groups(const void *a, const void *b)
> +{
> + const char *A = a;
> + const char *B = b;
> +
> + return strcmp(A, B);
a and b are not strings here. They are group_data pointers.
I think what you want is
From: Minfei Huang
For some arch, kexec shall map the reserved pages, then use them, when
we try to start the kdump service.
Now kexec will never unmap the reserved pages, once it fails to continue
starting the kdump service.
Make a pair of reserved pages in kdump starting path, whatever kexec
On Tue, Jun 23, 2015 at 10:11:19AM +0200, Pali Rohár wrote:
> This commit fix kernel crash when probing for rfkill devices in dell-laptop
> driver failed. Function free_page() was incorrectly used on struct page *
> instead of virtual address of SMI buffer.
>
> This commit also simplify
On Wed, Jun 24, 2015 at 07:58:30PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 24, 2015 at 10:10:17AM -0700, Paul E. McKenney wrote:
> > > The thing is, once you start bailing on this condition your 'queue'
> > > drains very fast and this is around the same time sync_rcu() would've
> > > released
On Thu, 21 May 2015 13:30:08 -0400
Josef Bacik wrote:
> V1->V2:
> -renamed the option to --by-comm, added it to trace-cmd report --profile as
> well
> -fixed up the string hash
Or break it ;-)
> -changed it to merge all events after the fact so it's less error prone
> diff --git
2015-06-25 1:24 GMT+09:00 Ming Lei :
> On Wed, Jun 24, 2015 at 10:34 PM, Akinobu Mita wrote:
>> Hi Ming,
>>
>> 2015-06-24 18:46 GMT+09:00 Ming Lei :
>>> On Sun, Jun 21, 2015 at 9:52 PM, Akinobu Mita
>>> wrote:
ctx->index_hw is zero for the CPUs which have never been onlined since
the
On Wed, Jun 24, 2015 at 5:07 PM, Andy Lutomirski wrote:
> On Wed, Jun 24, 2015 at 3:26 PM, Paul Turner wrote:
>> This is a fairly small series demonstrating a feature we've found to be quite
>> powerful in practice, "restartable sequences".
>>
>
> On an extremely short glance, I'm starting to
On Tue, 23 Jun 2015 16:06:39 -0700
Josef Bacik wrote:
> I needed to track down a very slow memory leak so I adapted the same approach
> trace-cmd profile uses to track kernel memory allocations. You run this with
>
> trace-cmd kmemleak
Note, I'm still playing with this.
>
> and then you can
Hi Robert,
On Tue, Jun 23, 2015 at 10:41:33PM +0200, Robert Jarzmik wrote:
> Richard Weinberger writes:
>
> > Am 17.06.2015 um 20:41 schrieb Brian Norris:
> >> Have you tested this patch?
> >
> > nah, I don't own such a device.
> But I do. If you resend a patch, please Cc me. You can even ask
On Wed, Jun 24, 2015 at 7:14 PM, Steven Rostedt wrote:
>
> I don't think it will complicate things even if the API changes. The distros
> will have to deal with that fall out. Mainline only cares about its own
> regressions. But any API changes would only be done for good reasons, and give
> the
On Tue, Jun 23, 2015 at 08:07:41AM -0700, Andy Lutomirski wrote:
>
> FWIW, once there are real distros with kdbus userspace enabled,
> reviewing kdbus gets more complicated -- we'll be in the position
> where merging kdbus in a different form from that which was proposed
> will break existing
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, June 25, 2015 3:49 AM
> To: Eric Auger
> Cc: Joerg Roedel; Avi Kivity; Wu, Feng; k...@vger.kernel.org;
> linux-kernel@vger.kernel.org; pbonz...@redhat.com; mtosa...@redhat.com
> Subject:
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Wednesday, June 24, 2015 11:46 PM
> To: Alex Williamson
> Cc: Wu, Feng; Eric Auger; Avi Kivity; k...@vger.kernel.org;
> linux-kernel@vger.kernel.org; pbonz...@redhat.com; mtosa...@redhat.com
> Subject: Re: [v4
On Wed, Jun 24, 2015 at 11:50 AM, Vivien Didelot
wrote:
> This patch adds the glue between DSA and switchdev operations to add,
> delete and dump SWITCHDEV_OBJ_PORT_VLAN objects.
>
> This is a first step to link the "bridge vlan" command with hardware
> entries for DSA compatible switch chips.
>
From: Kan Liang
AVG_LATENCY(bit 38) is only available on MSR_OFFCORE_RSP0.
So the bit should be removed from RSP1 valid_mask.
Since RSP0 and RSP1 may have different valid_mask, intel_alt_er should
validate the config on the alternate offcore reg before replacing it.
Signed-off-by: Kan Liang
Linus,
>
> On the *other* side of the same conflict, I find an even more offensive
> commit,
> namely commit 4cd7c9479aff ("IB/mad: Add support for additional MAD info
> to/from drivers") which adds a BUG_ON() for a sanity check, rather than just
> returning -EINVAL or something sane like that.
Hi Dan,
On Thu, 25 Jun 2015 08:57:06 +1000 Stephen Rothwell
wrote:
>
> On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman wrote:
> >
> > On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell
> > wrote:
> > >
> > > After merging the modules tree, today's linux-next build (x86_64
> > > allmodconfig)
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that
From: "Luis R. Rodriguez"
This driver uses strong UC for the MMIO region, and ioremap_wc()
for the framebuffer to whitelist for the WC MTRR what can be changed
to WC. On PAT systems we don't need the MTRR call so just use
arch_phys_wc_add() there, this lets us remove all those ifdefs.
Lets also
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that
On Thu, Jun 25, 2015 at 07:55:45AM +0800, Jeff Chua wrote:
> On Thu, Jun 25, 2015 at 12:28 AM, Greg Kroah-Hartman
> wrote:
> > On Thu, Jun 25, 2015 at 12:22:47AM +0800, Jeff Chua wrote:
>
> >> Both sda and sdb have the same SSD model.
> >
> > That's a bug in your USB bridge chip, odds are it is
From: "Luis R. Rodriguez"
Replace a WC MTRR call followed by a UC MTRR "hole" call
with a single WC MTRR call and use strong UC to protect
the MMIO region and account for the device's architecture
and MTRR size requirements.
The atyfb driver relies on two overlapping MTRRs. It
does this to
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as
From: "Luis R. Rodriguez"
This has no functional changes, it just adjusts
the ioremap() call for the framebuffer to use
the same values we later use for the framebuffer,
this will make it easier to review the next change.
The size of the framebuffer varies but since this is
for PCI we *know*
From: "Luis R. Rodriguez"
Now that we have pci_iomap_wc() add the respective
devres helpers. These go unexported for now but
note that should they later be exported this
must go with EXPORT_SYMBOL_GPL().
Cc: Toshi Kani
Cc: Andy Lutomirski
Cc: Suresh Siddha
Cc: Ingo Molnar
Cc: Thomas
From: "Luis R. Rodriguez"
Andrew,
Forgive me for the TL;DR, I'm afraid I need to be crystal clear on this
patchset as its the most complex in the entire series. The skinny is that this
patchset addresses a complex work around with APIs now merged upstream going in
for v4.2, the driver
From: "Luis R. Rodriguez"
PCI BARs tell us whether prefetching is safe, but they don't say anything
about write combining (WC). WC changes ordering rules and allows writes to
be collapsed, so it's not safe in general to use it on a prefetchable
region.
Add pci_iomap_wc() and
On Wed, Jun 24, 2015 at 02:37:51PM +0200, Geert Uytterhoeven wrote:
> Hi James,
>
> On Thu, Jun 11, 2015 at 9:18 PM, James Simmons wrote:
> > From: John L. Hammond
> >
> > Originally socklnd_lib-linux.h contained linux specific
> > wrappers and defines but since the linux kernel is the
> > only
From: "Luis R. Rodriguez"
The driver doesn't use mtrr_add() or arch_phys_wc_add() but
since we know the framebuffer is isolated already on an
ioremap() we can take advantage of write combining for
performance where possible.
In this case there are a few motivations for this:
a) Take advantage
2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin :
>
> On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> > virtio_net paravirtualized driver does not have a tx_timeout() function to
> > guarantee that the driver will recover properly after receiving a timeout
> > during a transmission
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as
From: "Luis R. Rodriguez"
This lets drivers take advantage of PAT when available. This
should help with the transition of converting video drivers over
to ioremap_wc() to help with the goal of eventually using
_PAGE_CACHE_UC over _PAGE_CACHE_UC_MINUS on x86 on
ioremap_nocache() (de33c442e titled
From: "Luis R. Rodriguez"
Boris,
This patchset is part of the long haul of series that addresses removal of
direct use of MTRR and transforms drivers over to use PAT interfaces when
available [0]. Other than this series there is only one more pending series for
that effort, the other one being
On Fri, Jun 19, 2015 at 3:22 PM, Luis R. Rodriguez wrote:
> Tomi, Dave, Andy,
>
> Its' been one month now since posting the last unmodified version
> (other than commit log) of this series [0] and no word or follow up
> from Ville. The merge window is closing in and other than the PCI
> changes
On Wed, 2015-06-24 at 16:11 +0100, Peter Griffin wrote:
> This is used in conjunction with the STV0367 demodulator on
> the STV0367-NIM-V1.0 NIM card which can be used with the STi
> STB SoC's.
Barely associated to this specific patch, but for
dvb-pll.c, another thing that seems possible is to
On Wed, 2015-06-24 at 17:58 -0700, Luis R. Rodriguez wrote:
> On Wed, Jun 24, 2015 at 5:52 PM, Benjamin Herrenschmidt
> wrote:
> > On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
> >>
> >> OK thanks I'll proceed with these patches then.
> >>
> >> > As for user mappings,
> >>
> >>
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Wednesday, June 24, 2015 10:06 PM
>
> On Wednesday, June 24, 2015 11:02:10 AM Lv Zheng wrote:
> > ACPICA commit 7aa598d711644ab0de5f70ad88f1e2de253115e4
> >
> > The following commit is reported to have broken s2ram on some
On Wed, 24 Jun 2015 16:19:33 -0700
Cong Wang wrote:
> For compatibility, the sched_switch event is not touched.
Yes, and sched_out() should not be added.
>
> Cc: Steven Rostedt
> Cc: Ingo Molnar
> Cc: Peter Zijlstra
> Signed-off-by: Cong Wang
> Signed-off-by: Cong Wang
> ---
>
On Wed, 2015-06-24 at 18:38 +0200, Luis R. Rodriguez wrote:
> On Wed, Jun 24, 2015 at 08:42:23AM +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2015-06-19 at 15:08 -0700, Luis R. Rodriguez wrote:
> > > From: "Luis R. Rodriguez"
> > >
> > > PCI BARs tell us whether prefetching is safe, but they
On Wed, 24 Jun 2015 23:29:30 +0200
Peter Zijlstra wrote:
> On Wed, Jun 24, 2015 at 01:14:18PM -0700, Stephen Boyd wrote:
> > John Stultz reported an RCU splat on ARM with ipi trace events
> > enabled. It looks like the same problem exists on ARM64.
> >
> > At this point in the IPI handling path
On Wed, 24 Jun 2015 14:56:49 -0700
"Luck, Tony" wrote:
> So the question is - how can we update the trace event to include these
> new wider fields with the minimum pain to applications that look at it?
> I don't know if there are any other consumers besides rasdaemon at the
> moment ... but we
On Wed, 2015-06-17 at 19:13 -0400, Dan Williams wrote:
> A new sub-system in support of non-volatile memory storage devices.
>
> Stephen, please add libnvdimm-for-next to -next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm libnvdimm-for-next
>
> Changes since v6 [1]:
>
> 1/
On Wed, Jun 24, 2015 at 5:52 PM, Benjamin Herrenschmidt
wrote:
> On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
>>
>> OK thanks I'll proceed with these patches then.
>>
>> > As for user mappings,
>>
>> Which APIs were you considering in this regard BTW?
>
> mmap of the generic
On Wed, 2015-06-24 at 17:16 -0700, Dave Hansen wrote:
> From: Dave Hansen
>
> I have a _tiny_ microbenchmark that sits in a loop and writes
> single bytes to a file. Writing one byte to a tmpfs file is
> around 2x slower than reading one byte from a file, which is a
> _bit_ more than I expecte.
On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
>
> OK thanks I'll proceed with these patches then.
>
> > As for user mappings,
>
> Which APIs were you considering in this regard BTW?
mmap of the generic /sys/bus/pci/.../resource*
> > maybe the right thing to do is to let us do
Currently, compaction works as following.
1) migration scanner scans from zone_start_pfn to zone_end_pfn
to find migratable pages
2) free scanner scans from zone_end_pfn to zone_start_pfn to
find free pages
3) If both scanner crossed, compaction is finished.
This algorithm has some drawbacks. 1)
Currently, freescanner doesn't scan non-movable pageblock, because if
freepages in non-movable pageblock are exhausted, another movable
pageblock would be used for non-movable allocation and it could cause
fragmentation.
But, we should know that watermark check for compaction doesn't consider
Recently, I got a report that android get slow due to order-2 page
allocation. With some investigation, I found that compaction usually
fails and many pages are reclaimed to make order-2 freepage. I can't
analyze detailed reason that causes compaction fail because I don't
have reproducible
Signed-off-by: Joonsoo Kim
---
mm/compaction.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/mm/compaction.c b/mm/compaction.c
index 9c5d43c..2d8e211 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -510,6 +510,10 @@ isolate_fail:
if (locked)
Compaction deferring was introduced to reduce overhead of compaction
when compaction attempt is expected to fail. But, it has a problem.
Whole zone is rescanned after some compaction attempts are deferred and
this rescan overhead is quite big. And, it imposes large latency to one
random requestor
Further compaction attempt is deferred when some of compaction attempts
already fails. But, after some number of trial are skipped, compaction
restarts work to check whether compaction is now possible or not. It
scans whole range of zone to determine this possibility and if compaction
possibility
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Thursday, June 25, 2015 7:57 AM
>
> On Wednesday, June 24, 2015 11:02:54 AM Lv Zheng wrote:
> > ACPICA commit 368eb60778b27b6ae94d3658ddc902ca1342a963
> > ACPICA commit 70f62a80d65515e1285fdeeb50d94ee6f07df4bd
> >
> > The
Now, compaction algorithm become powerful. Migration scanner traverses
whole zone range. So, old threshold for depleted zone which is designed
to imitate compaction deferring approach isn't appropriate for current
compaction algorithm. If we adhere to current threshold, 1, we can't
avoid excessive
Now, we have a way to determine compaction depleted state and compaction
activity will be limited according this state and depletion depth so
compaction overhead would be well controlled without compaction deferring.
So, this patch remove compaction deferring completely.
Various functions are
Rename check function and move one outer condition check to this function.
There is no functional change.
Signed-off-by: Joonsoo Kim
---
mm/compaction.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/mm/compaction.c b/mm/compaction.c
index 2d8e211..dd2063b 100644
---
Scanning pageblock is stopped at the middle of pageblock if enough
pages are isolated. In the next run, it begins again at this position
and if it find that there is no isolation candidate from the middle of
pageblock to end of pageblock, it updates skip-bit. In this case,
scanner doesn't start at
Scanner's cached pfn is used to determine the start position of scanner
at next compaction run. Current cached pfn points the skipped pageblock
so we uselessly checks whether pageblock is valid for compaction and
skip-bit is set or not. If we set scanner's cached pfn to next pfn of
skipped
The following changes since commit
d4a4f75cd8f29cd9464a5a32e9224a91571d6649:
Linux 4.1-rc7 (2015-06-07 20:23:50 -0700)
are available in the git repository at:
git://git.lwn.net/linux-2.6.git tags/docs-for-linus
for you to fetch changes up to 36f95a0b34cb980dcfff9c1082ca5d8f0dc5e78b:
On Wed, Jun 24, 2015 at 4:54 PM, Mathieu Desnoyers
wrote:
>
> OK, see below. This time the fault occurred at an unaligned address.
> It fails on the !pte_present(*pte_ref) check.
So every time, %rcx is 0x001fb.
Once, your rdx value (which is remaining bytes after the movsq) was 3,
the other two
Hello Paul,
On Thu, Jun 25, 2015 at 2:00 AM, Paul Gortmaker
wrote:
> [Re: [PATCH v7 00/14] crypto: add a new driver for Marvell's CESA] On
> 22/06/2015 (Mon 15:59) Herbert Xu wrote:
>
>> On Mon, Jun 22, 2015 at 09:23:36AM +0200, Boris Brezillon wrote:
>> > Hi Herbert,
>> >
>> > On Sun, 21 Jun
- On Jun 24, 2015, at 7:54 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Jun 24, 2015, at 3:15 PM, Linus Torvalds
> torva...@linux-foundation.org
> wrote:
>
>> On Wed, Jun 24, 2015 at 11:49 AM, Mathieu Desnoyers
>> wrote:
>>>
>>> Here is the output. I added the
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Thursday, June 25, 2015 7:24 AM
> To: Zheng, Lv
>
> On Wednesday, June 24, 2015 04:05:42 PM Rafael J. Wysocki wrote:
> > On Wednesday, June 24, 2015 11:02:10 AM Lv Zheng wrote:
> > > ACPICA commit
Hi,
> From: Christoph Hellwig [mailto:h...@infradead.org]
> Sent: Wednesday, June 24, 2015 8:56 PM
>
> On Wed, Jun 24, 2015 at 11:02:03AM +0800, Lv Zheng wrote:
> > ACPICA commit cb3d1c79f862cd368d749c9b8d9dced40111b0d0
> >
> > __FUNCTION__ is MSVC only, in Linux, it is __func__. Lv Zheng.
> >
>
Hello,
This is a trivial series that do some changes to the dependency for the
ChromeOS EC drivers Kconfig symbols. The patches are on top of Paul's
patch "mfd: fix dependency warning for CHROME_PLATFORMS on !X86, !ARM":
https://lkml.org/lkml/2015/6/20/219.
Paul fixed a warning about unmet
The ChromeOS EC SPI transport driver has a dependency on OF because it
uses some OF helpers from the header. But there isn't a
need for an explicit dependency since the header has stub functions if
CONFIG_OF is not defined.
Also, MFD_CROS_EC_SPI already depends on MFD_CROS_EC which in turn has
a
The Chrome platform support depends on X86 || ARM because there are
only Chromebooks using those architectures. But only some drivers
depend on a given architecture, and the ones that do already have
a dependency on their specific Kconfig symbol entries.
An option is to also make CHROME_PLATFORMS
A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
(MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies (X86
|| ARM)
This happened because CHROME_PLATFORMS had a dependency on X86 || ARM but
that dependency was removed since there isn't a reason why
From: Dave Hansen
According to Jan Kara:
You can have ignored mask set without any of the
notification masks set and you are expected to clear the
ignored mask on the first IN_MODIFY event.
But, the only way we currently have to go and find if we need to
do this
1 - 100 of 1512 matches
Mail list logo
