- Original Message -
> From: "Steven Rostedt"
> To: linux-kernel@vger.kernel.org
> Cc: "Ingo Molnar" , "Andrew Morton"
> , "Peter Zijlstra"
> , "Frederic Weisbecker" , "Mathieu
> Desnoyers"
>
> Sent: Wednesday, February 26, 2014 2:01:40 PM
> Subject: [RFA][PATCH 0/4] tracing: Request
On 2/26/14, 1:53 PM, Andi Kleen wrote:
Is there some reason not to enable frame pointers?
It makes code slower.
Sure there is some overhead because of the push, mov, pop instructions
per function. But, take for example the simple program below. Compile
with and without frame pointers
gcc
> > Another issue is that you can't enable it on a lot of existing
> > libraries, sometimes not even with a recompile. For example
> > glibc assembler functions do not support it at all, which
> > is a very common case.
>
> They're mostly all leaf functions, so it doesn't matter much if
>
On Wednesday, February 26, 2014 11:49:05 AM Alan Stern wrote:
> On Wed, 26 Feb 2014, Rafael J. Wysocki wrote:
>
> > > I admit, there most likely _are_ devices that would get into trouble if
> > > the question ever did arise.
> >
> > Well, I kind of put that to a test by posting these two
- Original Message -
> From: "Steven Rostedt"
> To: "Mathieu Desnoyers"
> Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" , "Thomas
> Gleixner" , "Rusty
> Russell" , "David Howells" ,
> "Greg Kroah-Hartman"
>
> Sent: Wednesday, February 26, 2014 3:40:12 PM
> Subject: Re: [PATCH] Fix:
Hi
I'm getting a reproducible crash in kernel MGA DRM driver.
The crash happens in the following way:
drm_release is called
drm_release calls drm_master_put(_priv->master);
drm_master_put drops a reference and calls drm_master_destroy
drm_master_destroy calls drm_rmmap_locked to unmap the
On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
> +The other case that generates a #BR is when a BNDSTX instruction
> +attempts to save bounds to a BD entry marked as invalid. This is
> +an indication that no BT exists for this entry. In this case the
> +fault handler will allocate a new BT.
Hi
On Wed, Feb 26, 2014 at 12:55 AM, Jiri Kosina wrote:
> On Wed, 26 Feb 2014, Or Gerlitz wrote:
[...]
> That definitely can be verified, and I am putting it on my TODO list.
OK, thanks
> But let's make sure that we don't diverge from the original problem too
> much. Simple fact is that the
From: Bjørn Mork
Date: Wed, 26 Feb 2014 22:14:10 +0100
> David Miller writes:
>
>> From: Bjørn Mork
>> Date: Wed, 26 Feb 2014 13:13:12 +0100
>>
>>> fre...@asix.com.tw writes:
>>>
From: Freddy Xin
Add VID:DID for Lenovo OneLinkDock Gigabit LAN
>>>
>>> This is the same patch
On Wed, Feb 26, 2014 at 09:53:22PM +0100, Andi Kleen wrote:
> > Is there some reason not to enable frame pointers?
>
> It makes code slower.
>
> Especially on Atom CPUs, where it causes pipeline stalls, but
Yeah, but nobody sane cares about the in-order atom crap CPUs.
> also to some degree on
David Miller writes:
> From: Bjørn Mork
> Date: Wed, 26 Feb 2014 13:13:12 +0100
>
>> fre...@asix.com.tw writes:
>>
>>> From: Freddy Xin
>>>
>>> Add VID:DID for Lenovo OneLinkDock Gigabit LAN
>>
>> This is the same patch Keith Packard sent, but with a slighly different
>> description. I take
On Wed, Feb 26, 2014 at 12:11 PM, Matthew Garrett
wrote:
> The conclusion we came to at Plumbers was that this patchset was basically
> fine but that Linus hated the name "securelevel" more than I hate pickled
> herring, so after thinking about this for a few months I've come up with
> "Trusted
Quoting Tushar Behera (2014-02-18 22:24:34)
> S5M8767 chip has 3 crystal oscillators which are operated in the same
> as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
> support clocks in S5M8767.
>
> The patches are rebased on top of next-20130218.
These changes look good to
On 02/26/2014 05:52 AM, Alexandre Courbot wrote:
> On 02/25/2014 06:52 PM, Arend van Spriel wrote:
>> On 02/25/2014 03:13 AM, Alexandre Courbot wrote:
> +/* Wifi */
> +sdhci@7800 {
> +status = "okay";
> +bus-width = <4>;
> +broken-cd;
Hi Jens,
Any feedback on these?
--
Regards,
Alexander Gordeev
agord...@redhat.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On 2014-02-26 11:29, Christoph Hellwig wrote:
Hi all,
with blk-mq stabilizing in mainline and Jens using mtip32xx as tje major
example drivers in the past is there any progress on getting the
conversion finished and merged?
I'll pick up the pieces as soon as I get back and can test again. The
From: Arnd Bergmann
Date: Wed, 26 Feb 2014 12:01:53 +0100
> The state machine code in the elsa driver uses interruptible_sleep_on
> to wait for state changes, which is racy. A closer look at the possible
> states reveals that it is always used to wait for getting back into
> ARCOFI_NOP, so we
From: Arnd Bergmann
Date: Wed, 26 Feb 2014 12:01:54 +0100
> These two drivers use identical code for their procfs status
> file handling, which contains a small race against status
> data becoming available while reading the file.
>
> This uses wait_event_interruptible instead to fix this
>
From: Arnd Bergmann
Date: Wed, 26 Feb 2014 12:01:55 +0100
> The isdn core code uses a couple of wait queues with
> interruptible_sleep_on, which is racy and about to get
> removed from the kernel. Fortunately, we know for each case
> what we are waiting for, so they can all be converted to
> the
From: Arnd Bergmann
Date: Wed, 26 Feb 2014 12:01:51 +0100
> interruptible_sleep_on is racy and going away. This replaces the one use
> in the firestream driver with the appropriate wait_event_interruptible
> variant.
>
> Signed-off-by: Arnd Bergmann
> Acked-by: Chas Williams
Applied.
--
To
From: Arnd Bergmann
Date: Wed, 26 Feb 2014 12:01:52 +0100
> interruptible_sleep_on is racy and going away. In case of pcbit,
> the driver would run into a timeout if the card is initialized
> before we start waiting for it. This uses wait_event to fix the
> race. In order to do this, the state
On Wed, Feb 26, 2014 at 12:57 PM, Arnd Bergmann wrote:
> On Wednesday 26 February 2014 12:48:17 Bjorn Helgaas wrote:
>> On Mon, Feb 24, 2014 at 4:00 AM, Arnd Bergmann wrote:
>> > Hi Magnus,
>> >
>> > I noticed during randconfig testing that you enabled DMABOUNCE for the
>> > pci-rcar-gen2 driver
Hi,
On 26/02/2014 at 18:39:04 +0100, Maxime Ripard wrote :
> Hi Alexandre,
>
> On Wed, Feb 26, 2014 at 06:01:08PM +0100, Alexandre Belloni wrote:
> > This corrects the example by removing the unit-address, as suggested by Mark
> > Rutland in
> >
On 02/26/2014 11:17 AM, Dave Hansen wrote:
> On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
>> +Bounds Directory (BD) and Bounds Tables (BT) are stored in
>> +application memory and are allocated by the application (in case
>> +of kernel use, the structures will be in kernel memory). The
>> +bound
On Wed, Feb 26, 2014 at 12:51:57PM +, Lee Jones wrote:
> > The tnetv107x platform is getting removed, so this driver
> > is not needed any more.
> >
> > Signed-off-by: Arnd Bergmann
> > Cc: Samuel Ortiz
> > Cc: Lee Jones
> > ---
> > drivers/mfd/Kconfig | 11 --
> > drivers/mfd/Makefile
Quoting Roger Quadros (2014-02-25 01:32:19)
> Hi Mike,
>
> On 02/25/2014 10:43 AM, Mike Turquette wrote:
> > Quoting Roger Quadros (2014-02-20 03:40:01)
> >> The OMAP USB Host MFD driver no longer expects these non-existing
> >> clocks from the OMAP3 platform, so get rid of them.
> >
> > Looks
Gidday,
I've released man-pages-3.61 - man pages for Linux.
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
http://man7.org/linux/man-pages/changelog.html#release_3.61
A
On Wed, Feb 26, 2014 at 12:45 PM, Greg KH wrote:
> On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
>> Hi,
>>
>> i still wait for ACK's for the 32 bit VDSO time function support. Whats
>> the next step? Is there a way to apply it to the linux-git or linux-next
>> in near future?
> Is there some reason not to enable frame pointers?
It makes code slower.
Especially on Atom CPUs, where it causes pipeline stalls, but
also to some degree on others, because you lose one register and
spend a little bit of time setting it up, so making small
functions more expensive.
Another
From: Joe Perches
Date: Tue, 25 Feb 2014 13:35:53 -0800
> Add a new F: line for the intel subdirectories.
>
> This allows get_maintainers to avoid using git log
> and cc'ing people that have submitted clean-up style
> patches for all first level directories under
> drivers/net/ethernet/intel/
>
From: Bjørn Mork
Date: Wed, 26 Feb 2014 13:13:12 +0100
> fre...@asix.com.tw writes:
>
>> From: Freddy Xin
>>
>> Add VID:DID for Lenovo OneLinkDock Gigabit LAN
>
> This is the same patch Keith Packard sent, but with a slighly different
> description. I take that as another proof that we
Hi,
>>
>> +config PHY_XGENE
>> + tristate "APM X-Gene 15Gbps PHY support"
>> + depends on ARM64 || COMPILE_TEST
>> + select GENERIC_PHY
>
>
> depends on HAS_IOMEM and CONFIG_OF..
I will make it depends as "HAS_IOMEM && OF && (ARM64 || COMPILE_TEST)
>>
>> +/* PLL Clock Macro
On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
> Hi,
>
> i still wait for ACK's for the 32 bit VDSO time function support. Whats
> the next step? Is there a way to apply it to the linux-git or linux-next
> in near future?
I thought this was already in the tip tree. Didn't the
> +#ifdef CONFIG_S390
> + /*
> + * MADV_HUGEPAGE is broken after s390_enable_sie(), qemu
> + * blindly does madvise(MADV_HUGEPAGE) for for all kvm pages
> + * and expects it must fail on s390. Avoid a possible SIGSEGV
> + * until
Mathieu, you should have added a v2 to the subject ie: [PATCH V2]
Rusty,
If you want to take this, please add my
Acked-by: Steven Rostedt
-- Steve
On Fri, 14 Feb 2014 00:18:26 -0500
Mathieu Desnoyers wrote:
> Users have reported being unable to trace non-signed modules loaded
> within a
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
for-next
Head SHA1: 62183dcac539a14ed0a820b8392db353d72a7d7e
Satoru Takeuchi (1):
ktest: Set CLOSE_CONSOLE_SIGNAL in the kvm.conf
tools/testing/ktest/examples/kvm.conf | 4
1 file changed, 4
On Wed, Feb 26, 2014 at 01:14:58PM -0700, David Ahern wrote:
> Does WRL or Yocto fall into that 'standard distro' comment? Fairly easy to
> enable frame-pointers.
Yeah, same for Gentoo, I always build world with frame-pointers enabled.
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, 25 Feb 2014 21:21:18 -0500
MUNEDA Takahiro wrote:
> Hmm, it seems that we need a following patch as well.
> Or, please merge with the orignal patch.
I folded this fix in, here's the final:
>From 62183dcac539a14ed0a820b8392db353d72a7d7e Mon Sep 17 00:00:00 2001
From: Satoru Takeuchi
On Wed, Feb 26, 2014 at 07:15:11PM +0100, Andrew Jones wrote:
> When we update a vcpu's local clock it may pick up an NTP correction.
> We can't wait an indeterminate amount of time for other vcpus to pick
> up that correction, so commit 0061d53daf26f introduced a global clock
> update. However,
On 02/26/2014 11:50 AM, Ben Greear wrote:
> This is from the ath10k tree, which was recently rebased on top of
> 3.14.0-rc4.
>
> I'm getting the error below, but I cannot find any reference to 'spinlokk'
> in the source tree. The build tree has two mentions, but these are
> auto-generated
>
On Wed, Feb 26, 2014 at 07:15:12PM +0100, Andrew Jones wrote:
> commit 0061d53daf26f introduced a mechanism to execute a global clock
> update for a vm. We can apply this periodically in order to propagate
> host NTP corrections. Also, if all vcpus of a vm are pinned, then
> without an additional
On Wed, Feb 26, 2014 at 12:14 PM, David Ahern wrote:
> On 2/26/14, 12:25 PM, Andy Lutomirski wrote:
>>
>> On Wed, Feb 26, 2014 at 11:19 AM, David Ahern wrote:
>>>
>>> On 2/26/14, 11:59 AM, Andy Lutomirski wrote:
>>>
I wonder if anyone who uses perf for userspace profiling *ever* uses
On Wed, 26 Feb 2014 14:46:47 +0100
"Lorenz Bucher" wrote:
> Solves an issue with dfs where servers using package signing are
> mixed with servers which don't use package signing.
>
> Signed-off-by: Lorenz Bucher
> ---
> fs/cifs/connect.c |3 +++
> 1 file changed, 3 insertions(+)
>
> diff
> The only case we need to handle is when the interface is brought down,
> suspend_halted=true will also power down the PHY, you reboot into
> u-boot, and you attempt a network boot right after that, in that case
> the PHY interface is still powered down and this does not work.
Correct. And since
On 02/25/2014 10:02 PM, Viresh Kumar wrote:
On 26 February 2014 07:18, Saravana Kannan wrote:
On 02/25/2014 02:41 PM, Rafael J. Wysocki wrote:
And is "fully initialized" actually well defined?
The point in add dev/hot plug path after which we will no longer change
policy fields without
cpufreq_frequency_get_table() is called from all callers of
__cpufreq_stats_create_table(). So, move it inside.
Suggested-by: Viresh Kumar
Signed-off-by: Saravana Kannan
---
drivers/cpufreq/cpufreq_stats.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
diff
__cpufreq_stats_create_table always gets pass the valid and real policy
struct. So, there's no need to call cpufreq_cpu_get() to get the policy
again.
Acked-by: Viresh Kumar
Signed-off-by: Saravana Kannan
---
drivers/cpufreq/cpufreq_stats.c | 12 +---
1 file changed, 1 insertion(+), 11
Remove sysfs group if __cpufreq_stats_create_table() fails after creating
one.
Acked-by: Viresh Kumar
Signed-off-by: Saravana Kannan
---
drivers/cpufreq/cpufreq_stats.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq_stats.c
Permitting write access to MSRs allows userspace to modify the running
kernel. Prevent this if trusted_kernel is true. Based on a patch by Kees
Cook.
Cc: Kees Cook
Signed-off-by: Matthew Garrett
---
arch/x86/kernel/msr.c | 8
1 file changed, 8 insertions(+)
diff --git
UEFI Secure Boot provides a mechanism for ensuring that the firmware will
only load signed bootloaders and kernels. Certain use cases may also
require that the kernel prevent userspace from inserting untrusted kernel
code at runtime. Add a configuration option that enforces this automatically
when
We have no way of validating what all of the Asus WMI methods do on a
given machine, and there's a risk that some will allow hardware state to
be manipulated in such a way that arbitrary code can be executed in the
kernel. Prevent that if trusted_kernel is true.
Signed-off-by: Matthew Garrett
On 2/26/14, 12:25 PM, Andy Lutomirski wrote:
On Wed, Feb 26, 2014 at 11:19 AM, David Ahern wrote:
On 2/26/14, 11:59 AM, Andy Lutomirski wrote:
I wonder if anyone who uses perf for userspace profiling *ever* uses
FP and gets away with it. There's precious little userspace software
compiled
Provide a boolean runtime configuration option for restricting userspace's
ability to modify the running kernel. This can be used when some external
validation of the kernel's state has been performed.
Signed-off-by: Matthew Garrett
---
Documentation/kernel-parameters.txt | 6 ++
Allowing users to write to address space provides mechanisms that may permit
modification of the kernel at runtime. Prevent this if trusted_kernel is
true.
Signed-off-by: Matthew Garrett
---
drivers/char/mem.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/char/mem.c
IO port access would permit users to gain access to PCI configuration
registers, which in turn (on a lot of hardware) give access to MMIO register
space. This would potentially permit root to trigger arbitrary DMA, so lock
it down when trusted_kernel is true
Signed-off-by: Matthew Garrett
---
From: Josh Boyer
This option allows userspace to pass the RSDP address to the kernel, which
makes it possible for a user to execute arbitrary code in the kernel.
Disable this when trusted_kernel is true.
Signed-off-by: Josh Boyer
---
drivers/acpi/osl.c | 3 ++-
1 file changed, 2
custom_method effectively allows arbitrary access to system memory, making
it possible for an attacker to modify the kernel at runtime. Prevent this
if trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
drivers/acpi/custom_method.c | 4
1 file changed, 4 insertions(+)
diff --git
On Wed, Feb 26, 2014 at 12:12:06PM -0500, Johannes Weiner wrote:
> On Wed, Feb 26, 2014 at 09:54:22AM +, Mel Gorman wrote:
> > How about special casing the (alloc_flags & ALLOC_WMARK_LOW) check in
> > get_page_from_freelist to also ignore GFP_THISNODE? The NR_ALLOC_BATCH
> > will go further
If trusted_kernel is true, require that all modules have valid signatures.
Signed-off-by: Matthew Garrett
---
kernel/module.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/module.c b/kernel/module.c
index d24fcf2..e0220db 100644
--- a/kernel/module.c
+++
On Wed, 26 Feb 2014 13:23:56 +1030
Rusty Russell wrote:
> > The one that I replied to. I can't pull the module patch unless I get
> > an ack from Rusty.
>
> Ah, I applied it in my tree. Happy for you to take it though; here's
> the variant with an Acked-by from me instead of Signed-off-by if
kexec permits the loading and execution of arbitrary code in ring 0, which
permits the modification of the running kernel. Prevent this if
trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
kernel/kexec.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/kexec.c
Any hardware that can potentially generate DMA has to be locked down from
userspace in order to avoid it being possible for an attacker to modify
kernel code. This should be prevented if trusted_kernel has been
set. Default to paranoid - in future we can potentially relax this for
sufficiently
The conclusion we came to at Plumbers was that this patchset was basically
fine but that Linus hated the name "securelevel" more than I hate pickled
herring, so after thinking about this for a few months I've come up with
"Trusted Kernel". This flag indicates that the kernel is, via some
external
uswsusp allows a user process to dump and then restore kernel state, which
makes it possible to modify the running kernel. Disable this if
trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
kernel/power/user.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/power/user.c
I'm planning on testing this, hopefully today.
--Andy
On Wed, Feb 26, 2014 at 11:34 AM, Stefani Seibold wrote:
> Hi,
>
> i still wait for ACK's for the 32 bit VDSO time function support. Whats
> the next step? Is there a way to apply it to the linux-git or linux-next
> in near future?
>
> -
Commit-ID: f96a34e27df19335155394a235ea3a096bc52a71
Gitweb: http://git.kernel.org/tip/f96a34e27df19335155394a235ea3a096bc52a71
Author: Paul Gortmaker
AuthorDate: Thu, 6 Feb 2014 13:36:21 -0500
Committer: Frederic Weisbecker
CommitDate: Fri, 14 Feb 2014 17:59:17 +0100
nohz: ensure
Commit-ID: 8ba14654282ed6bb386d0a2f1ab329bfb293403f
Gitweb: http://git.kernel.org/tip/8ba14654282ed6bb386d0a2f1ab329bfb293403f
Author: Viresh Kumar
AuthorDate: Mon, 10 Feb 2014 17:09:54 +0100
Committer: Frederic Weisbecker
CommitDate: Fri, 14 Feb 2014 17:59:14 +0100
timer: Spare IPI
Add a simple twl_i2c_read/write_u16 wrapper over
the twl_i2c_read/write, which is similar to the
twl_i2c_read/write_u8 wrapper.
Signed-off-by: Sebastian Reichel
Acked-by: Lee Jones
---
include/linux/i2c/twl.h | 12
1 file changed, 12 insertions(+)
diff --git
On 02/25/2014 09:06 PM, Viresh Kumar wrote:
On 26 February 2014 09:08, Saravana Kannan wrote:
__cpufreq_stats_create_table always gets pass the valid and real policy
struct. So, there's no need to call cpufreq_cpu_get() to get the policy
again.
Change-Id:
Simplify reading and writing of 16 bit TWL registers in the
driver by using twl_i2c_read_u16 and twl_i2c_write_u16.
Signed-off-by: Sebastian Reichel
Acked-by: Lee Jones
---
drivers/mfd/twl4030-madc.c | 39 ---
1 file changed, 8 insertions(+), 31 deletions(-)
This is a driver for an A/D converter, which belongs into
drivers/iio/adc.
Signed-off-by: Sebastian Reichel
Acked-by: Lee Jones
---
drivers/iio/adc/Kconfig | 10 ++
drivers/iio/adc/Makefile| 1 +
drivers/{mfd => iio/adc}/twl4030-madc.c | 0
Add devicetree binding documentation for twl4030-madc
analog digital converter.
Signed-off-by: Sebastian Reichel
---
.../devicetree/bindings/iio/adc/twl4030-madc.txt | 24 ++
1 file changed, 24 insertions(+)
create mode 100644
Hi,
This is RFCv4 for converting twl4030-madc to the IIO API and
adding DT support. The patchset compiles and has been tested
on my Nokia N900.
Changes since RFCv3 [0]:
* Added Acked-by from Lee Jones (MFD subsystem maintainer)
to twl_i2c_read/write_u16 patches
* Fixed style issues found by
This converts twl4030-madc module to use the Industrial IO ADC
framework and adds device tree support.
Signed-off-by: Sebastian Reichel
---
drivers/mfd/twl4030-madc.c | 127 +
1 file changed, 118 insertions(+), 9 deletions(-)
diff --git
Update twl4030-madc driver to use managed resources.
Signed-off-by: Sebastian Reichel
Acked-by: Lee Jones
---
drivers/mfd/twl4030-madc.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/mfd/twl4030-madc.c b/drivers/mfd/twl4030-madc.c
index
Some style fixes in twl4030-madc driver.
Reported-by: Jonathan Cameron
Signed-off-by: Sebastian Reichel
---
drivers/mfd/twl4030-madc.c | 106 ++-
include/linux/i2c/twl4030-madc.h | 2 +-
2 files changed, 51 insertions(+), 57 deletions(-)
diff --git
On Wednesday 26 February 2014 12:48:17 Bjorn Helgaas wrote:
> On Mon, Feb 24, 2014 at 4:00 AM, Arnd Bergmann wrote:
> > Hi Magnus,
> >
> > I noticed during randconfig testing that you enabled DMABOUNCE for the
> > pci-rcar-gen2 driver as posted in this patch
> > https://lkml.org/lkml/2014/2/5/30
On Mon, 24 Feb 2014 17:58:18 + (UTC)
Mathieu Desnoyers wrote:
> > The one that I replied to. I can't pull the module patch unless I get
> > an ack from Rusty.
>
> Do you mean the internal API semantic change you propose for tracepoints ?
> If yes, then how do you consider this a fix worthy
This is from the ath10k tree, which was recently rebased on top of
3.14.0-rc4.
I'm getting the error below, but I cannot find any reference to 'spinlokk'
in the source tree. The build tree has two mentions, but these are
auto-generated
from what I can tell:
[greearb@ben-dt2 linux-ath.x64]$
On Mon, Feb 24, 2014 at 4:00 AM, Arnd Bergmann wrote:
> Hi Magnus,
>
> I noticed during randconfig testing that you enabled DMABOUNCE for the
> pci-rcar-gen2 driver as posted in this patch https://lkml.org/lkml/2014/2/5/30
>
> I didn't see the original post unfortunately, but I fear we have to
>
From: "David E. Box"
Some loadable modules only need IOSF access on the platforms where it exists.
Provide dummy functions to allow these modules to compile and load on the
platforms where it doesn't exist.
Signed-off-by: David E. Box
---
arch/x86/include/asm/iosf_mbi.h | 33
From: "David E. Box"
This patch series adds missing functionalty that mostly affected loadable
modules.
The first patch adds dummy functions to allow drivers not completely
dependant on the IOSF MBI driver to compile on systems that don't have it.
The second ensures the availabilty of the MBI
From: "David E. Box"
The IOSF Mailbox interface is an access mechanism used by multiple drivers to
communicate with key configuration registers on new Intel SOC platforms. The
interface is ubiquitous enough that we need to ensure the availability of the
driver in non-EXPERT configured x86
If the resource hasn't been allocated yet, pci_find_parent_resource() is
documented as returning the region "where it should be allocated from."
This is impossible in general because there may be several candidates: a
prefetchable BAR can be put in either a prefetchable or non-prefetchable
window,
When assigning addresses to resources, mark them with IORESOURCE_UNSET
before we start and clear IORESOURCE_UNSET if assignment is successful.
That means that if we print the resource during assignment, we will show
the size, not a meaningless address.
Also, clear IORESOURCE_UNSET if we do assign
Don't rely on BAR contents when the command register says the BAR is
disabled.
If we receive a PCI device from firmware (or a hot-added device that was
just powered up) with the MEMORY or IO enable bits in the PCI command
register cleared, there's no reason to believe the BARs contain valid
Don't enable memory or I/O decoding if we haven't assigned or claimed the
BAR's resource.
If we enable decoding for a BAR that hasn't been assigned an address, we'll
likely cause bus conflicts. This declines to enable decoding for resources
with IORESOURCE_UNSET.
Note that drivers can use
Clear IORESOURCE_UNSET when we assign an address to a resource, not when we
write the address to the BAR.
Also, drop the "BAR %d: set to %pR" message; this is mostly redundant with
the "BAR %d: assigned %pR" message from pci_assign_resource().
Signed-off-by: Bjorn Helgaas
---
On 2/26/2014 11:29 AM, Christoph Hellwig wrote:
> Hi all,
>
> with blk-mq stabilizing in mainline and Jens using mtip32xx as tje major
> example drivers in the past is there any progress on getting the
> conversion finished and merged?
We are working on few changes in mtip32xx. After that, we
It's very common to have normal block comments for the initial
comments of a file description preface.
So for files in drivers/net and net/ don't emit a warning when
the first comment block in the file uses the normal block comment
style and not the networking block comment style.
Signed-off-by:
From: Russ Dill
Enable hibernation for ARM architectures and provide ARM
architecture specific calls used during hibernation.
The swsusp hibernation framework depends on the
platform first having functional suspend/resume.
Then, in order to enable hibernation on a given platform, a
Instead of array indexing $_, use temporary variables like
all the other subroutines in the script use.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 29 -
1 file changed, 20 insertions(+), 9 deletions(-)
diff --git a/scripts/checkpatch.pl
If the IORESOURCE_UNSET bit is set, it means we haven't assigned an address
yet, so don't try to claim the region.
Also, make the error messages more uniform and add info about which BAR is
involved.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/setup-res.c | 15 ++-
1 file
Patches adding support for hibernation on ARM
- ARM hibernation / suspend-to-disk
- Change soft_restart to use non-tracing raw_local_irq_disable
Patches based on v3.13 tag, verified hibernation on beaglebone black on a
branch based on 3.13 merged with initial omap support from Russ Dill which
On Wed, Feb 26, 2014 at 08:27:36PM +0100, Christian Borntraeger wrote:
> On 26/02/14 19:06, Oleg Nesterov wrote:
> > On 02/26, Alex Thorlton wrote:
> >>
> >> + * MADV_HUGEPAGE after PRCTL_THP_DISABLE is broken on s390 because
> >> + * qemu blindly does madvise(MADV_HUGEPAGE) after
On Tue, Feb 25, 2014 at 02:03:36PM -0800, Eric W. Biederman wrote:
> "J. Bruce Fields" writes:
>
> > On Mon, Feb 24, 2014 at 04:01:29PM -0800, Eric W. Biederman wrote:
> >> Miklos Szeredi writes:
> >>
> >> >
> >> > You can optimize this by including the negative check within the above
> >> >
Sometimes we have a struct resource where we know the type (MEM/IO/etc.)
and the size, but we haven't assigned address space for it. The
IORESOURCE_UNSET flag is a way to indicate this situation. For these
"unset" resources, the start address is meaningless, so print only the
size, e.g.,
-
Use of tracers in local_irq_disable is causes recursive aborts when
called with irqs disabled and using a temporary stack (hibernation).
Replace local_irq_disable with raw_local_irq_disable instead to
avoid tracers.
Signed-off-by: Sebastian Capella
Cc: Russell King
Cc: Andrew Morton
Cc: Thomas
Check to make sure we don't update a BAR with an address we haven't
assigned.
If we haven't assigned an address to a resource, we shouldn't write it to a
BAR. This isn't a problem for the usual path via pci_assign_resource(),
which clears IORESOURCE_UNSET before calling pci_update_resource(),
I'm trying to unify the way we handle unassigned PCI BARs, i.e., resources
where we know the type and size, but we haven't assigned an address yet.
The PCI core and the various architectures don't really have a consistent
way of dealing with these.
Many places currently use "res->start == 0" to
301 - 400 of 1722 matches
Mail list logo
