On Wed, 2015-06-24 at 10:57 +0800, Alex Hung wrote:
> --- /dev/null
> +++ b/drivers/platform/x86/asus-rbtn.c
> +MODULE_ALIAS("acpi*:ATK4001:*");
This looked odd. It turned out this is the pattern that
scripts/mod/file2alias.c::do_acpi_entry() creates.
> +static const struct acpi_device_id asusr
On 06/24/2015 10:36 PM, Paul Bolle wrote:
> On Tue, 2015-06-23 at 11:00 -0700, Moritz Fischer wrote:
>> +MODULE_ALIAS("platform:xilinx-mailbox");
>
> So I think this MODULE_ALIAS() is only useful if, in short, there's a
> corresponding platform_device created. Ie, a platform_device with a
> name "
Hi Rusty,
After merging the modules tree, today's linux-next build (powerpc
allnoconfig) failed like this:
kernel/params.c:628:6: error: redefinition of 'kernel_param_lock'
void kernel_param_lock(struct module *mod)
^
In file included from include/linux/module.h:18:0,
from
* Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> On built-in kernels this warning will always splat as this is part
> of the module init. Fix that by shifting the PAT requirement check
> out under the code that does the "quasi-probe" for the device. This
> device driver relies on an
* Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> WARN() may confuse users, fix that. ipath_init_one() is part the
> device's probe so this would only be triggered if a corresponding
> device was found.
>
> Signed-off-by: Luis R. Rodriguez
> ---
> drivers/infiniband/hw/ipath/ipath_
On Thu, 25 Jun 2015 01:03:05 +0900,
Linus Torvalds wrote:
>
> On Tue, Jun 23, 2015 at 9:17 AM, Yoshinori Sato
> wrote:
> >
> > Could you pull this tree?
> > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git for-4.2
>
> Welcome back for the h8300 tree... Well, almost:
>
> I was going to pull
On Wed, 24 Jun 2015, Greg KH wrote:
On Wed, Jun 24, 2015 at 10:39:52AM -0700, David Lang wrote:
On Wed, 24 Jun 2015, Ingo Molnar wrote:
And the thing is, in hindsight, after such huge flamewars, years down the line,
almost never do I see the following question asked: 'what were we thinking
m
On Thu, Jun 25, 2015 at 07:32:36AM +0100, Al Viro wrote:
> On Wed, Jun 24, 2015 at 10:50:10PM -0700, Jaegeuk Kim wrote:
>
> > Right, I missed merging the fix-up patch in linux-next into my pull-request.
> > At a glance, I think there is no problem; except 80 column width, though.
> >
> > Also, ag
Hi all,
I see Joerg has backported it to sles12 in the commoent of novel
bugzilla 856382, so I will only backport it to redhat el.
Thanks
Zhenhua
On 06/13/2015 02:47 PM, Joerg Roedel wrote:
Hi,
as David Woodhouse pointed out, my fixes and cleanups for
the original patch-set turned out to be a
Christoffer Dall writes:
> On Fri, Jun 19, 2015 at 01:23:48PM +0100, Alex Bennée wrote:
>> This adds support for userspace to control the HW debug registers for
>> guest debug. In the debug ioctl we copy the IMPDEF defined number of
>
> s/defined//
>
>> registers into a new register set called h
On Thu, Jun 25, 2015 at 3:33 AM, Guenter Roeck wrote:
> I have not tested it, but I think the following may fix the problem
> while avoiding any include problems. Since pt_regs is used in the file,
> one could argue that it should be declared.
Indeed. I tried that, but...
> --
> diff --git a/arc
On 06/23/2015 10:38 PM, David Woodhouse wrote:
On Tue, 2015-06-23 at 16:06 +0200, Joerg Roedel wrote:
On Tue, Jun 23, 2015 at 02:31:30PM +0100, David Woodhouse wrote:
However, it's still fairly gratuitous for all non-broken hardware, and
will tend to hide hardware and driver bugs during testing
Christoffer Dall writes:
> On Fri, Jun 19, 2015 at 01:23:46PM +0100, Alex Bennée wrote:
>> 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
On Wed, Jun 24, 2015 at 10:50:10PM -0700, Jaegeuk Kim wrote:
> Right, I missed merging the fix-up patch in linux-next into my pull-request.
> At a glance, I think there is no problem; except 80 column width, though.
>
> Also, agreed that I need to take a look at deleting the dentry to deal with
Christoffer Dall writes:
> On Fri, Jun 19, 2015 at 01:23:47PM +0100, Alex Bennée wrote:
>> 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. As we are no longer tied to the layout of the s
On Wed, Jun 24, 2015 at 10:39:52AM -0700, David Lang wrote:
> On Wed, 24 Jun 2015, Ingo Molnar wrote:
>
> >And the thing is, in hindsight, after such huge flamewars, years down the
> >line,
> >almost never do I see the following question asked: 'what were we thinking
> >merging
> >that crap??'.
On Thu, Jun 25, 2015 at 05:33:34AM +0100, Al Viro wrote:
> Said that, f2fs_symlink() looks odd - we create a directory entry *before*
> doing page_symlink(). And if it (or encryption) fails, I don't see anything
> that would remove that new directory entry. What are we ending up with
> in such c
This patch adds generic dts nodes for eTSEC0, eTSEC1 and eTSEC2.
Signed-off-by: Claudiu Manoil
Signed-off-by: Alison Wang
---
arch/arm/boot/dts/ls1021a-qds.dts | 20 ++
arch/arm/boot/dts/ls1021a-twr.dts | 20 ++
arch/arm/boot/dts/ls1021a.dtsi| 82
Hi Matthias and Mark,
May I have some review comments for this patch from you to get this
series moving forwards?
Thanks.
Pi-Cheng
On Wed, Jun 24, 2015 at 9:06 AM, Viresh Kumar wrote:
> Adding Mike's new email address..
>
> On 23-06-15, 23:31, Pi-Cheng Chen wrote:
>> On Mon, Jun 8, 2015 at 8:29
Am Mittwoch, 24. Juni 2015, 18:41:52 schrieb Greg Kroah-Hartman:
> 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 s
Am Donnerstag, 25. Juni 2015, 08:01:35 schrieb Martin Steigerwald:
> Am Mittwoch, 24. Juni 2015, 19:20:27 schrieb Linus Torvalds:
> > 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 de
On 25.06.2015 14:57, Vaibhav Hiremath wrote:
>
>
> 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:
>
>
Am Mittwoch, 24. Juni 2015, 19:20:27 schrieb Linus Torvalds:
> 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 a
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 fixu
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 t
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)
>>>
>>> Si
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 88p
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
---
drivers
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 b
* 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 ter
* 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 early
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 *ext
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 b/arch/arm/kernel/hw_breakpoint
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
compres
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"
prop
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 staging
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 t
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. I
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 KEY_RF
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
b/drivers/net/ethernet/freescale/
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 a2fd66d069d86d793e9
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, &h
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 will
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 this
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 allocating
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 th
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 a/trace-hash
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 b
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 thi
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 fo
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 d
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 user
> -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: Re:
> -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 08/1
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 b
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 n
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 accou
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 write-combining
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* thi
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 Gleixner
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 maintainer
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 pci_iomap_wc_range(
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 o
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 of
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 write-combining
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 write-combining
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 t
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 th
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
con
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,
> >>
> >> Which
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 p
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
> ---
> include/tr
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/ D
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 /sys/bu
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 wha
1 - 100 of 766 matches
Mail list logo
