On 05/14/2014 01:27 PM, Richard Weinberger wrote:
Am 14.05.2014 22:22, schrieb Sam Ravnborg:
On Wed, May 14, 2014 at 10:04:41PM +0200, Richard Weinberger wrote:
Am 14.05.2014 21:55, schrieb Sam Ravnborg:
On Wed, May 14, 2014 at 08:59:55PM +0200, Richard Weinberger wrote:
It is no longer neede
On 05/14/2014 07:34 PM, Thomas Gleixner wrote:
> On Wed, 14 May 2014, Carlos O'Donell wrote:
>
>> On 05/14/2014 03:03 PM, Michael Kerrisk (man-pages) wrote:
However, unless I'm sorely mistaken, the larger problem is that glibc
removed the futex() call entirely, so these man pages don't d
On Wed, May 14, 2014 at 10:17:49PM -0400, Theodore Ts'o wrote:
> On Thu, May 15, 2014 at 07:54:57AM +1000, Dave Chinner wrote:
> > On Tue, May 13, 2014 at 08:31:02PM +0200, Mateusz Guzik wrote:
> > > This helps hang troubleshooting efforts when only dmesg is available.
> >
> > I really don't think
The hwmon subsystem has been around for a while. Time to document
its kernel API.
Signed-off-by: Guenter Roeck
---
Documentation/hwmon/hwmon-kernel-api.txt | 107 +++
1 file changed, 107 insertions(+)
create mode 100644 Documentation/hwmon/hwmon-kernel-api.txt
diff
On Tue, 13 May 2014, Vince Weaver wrote:
> pe[32].sample_period=0xc0bd;
>
> Should it be possible to open an event with a large negative sample_period
> like that?
so this seems to be a real bug.
attr->sample_period is a u64 value, but internally it gets cast to
s64 and is
Remove support for building against ancient WIRELESS_EXT versions,
only leaving support for the current version: 22
---
drivers/staging/rtl8192u/ieee80211/ieee80211.h| 14 -
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c | 5 +--
drivers/staging/rtl8192u/ieee80211/ieee80211_wx.c |
Hi,
It's not a big deal but I've found that phy_base field of struct
l2x0_regs is not used anywhere.
I've removed it on my board. It seems to be working fine.
Why do we need physical address of L2 cache controller?
Is it removable?
8< --
>From cc
On Wed, 2014-05-14 at 15:11 -0400, Paul Gortmaker wrote:
> Given that, perhaps a separate change to sched_rt_runtime_exceeded()
> that works out the CPU from the rt_rq, and returns zero if it is a
> nohz_full cpu? Does that make sense? Then the nohz_full people won't
> get the throttling message
Hello,
On 05/15/2014 10:53 AM, Joonsoo Kim wrote:
On Tue, May 13, 2014 at 12:00:57PM +0900, Minchan Kim wrote:
Hey Joonsoo,
On Thu, May 08, 2014 at 09:32:23AM +0900, Joonsoo Kim wrote:
CMA is introduced to provide physically contiguous pages at runtime.
For this purpose, it reserves memory at
On Thu, May 15, 2014 at 10:53:01AM +0900, Joonsoo Kim wrote:
> On Tue, May 13, 2014 at 12:00:57PM +0900, Minchan Kim wrote:
> > Hey Joonsoo,
> >
> > On Thu, May 08, 2014 at 09:32:23AM +0900, Joonsoo Kim wrote:
> > > CMA is introduced to provide physically contiguous pages at runtime.
> > > For thi
Mēs esam DIAMOND ŠVEICES aizdevumu uzņēmumam sniedzot aizdevumus ar pasta
reklāma. Mēs piedāvājam dažāda veida aizdevumu (īstermiņa un ilgtermiņa
aizdevumi, individuālie aizņēmumi, aizdevumi uzņēmumiem utt.) Par 3% procentu
likmi. Mēs izsniegt aizdevumus cilvēkiem, kam nepieciešama ne neatkar
On 05/15/2014 02:23 AM, Andy Lutomirski wrote:
> On Wed, May 14, 2014 at 3:11 PM, Cyrill Gorcunov wrote:
>> On Wed, May 14, 2014 at 02:33:54PM -0700, Andy Lutomirski wrote:
>>> On Wed, May 14, 2014 at 2:31 PM, Andrew Morton
>>> wrote:
On Wed, 14 May 2014 17:11:00 -0400 Sasha Levin
wro
> I think it should do:
>
> if (status & 1)
> dse.mem_lvl = PERF_MEM_LVL_L1|PERF_MEM_LVL_HIT;
> else
> dse.mem_lvl = PERF_MEM_LVL_L1|PERF_MEM_LVL_MISS;
>
> Otherwise you have L1 as the level with no hit/miss info.
Agreed.
BTW the line before is also not always corect, and any ev
On Wed, 2014-05-14 at 18:32 -0700, Greg Kroah-Hartman wrote:
> On Wed, May 14, 2014 at 04:34:48PM -0500, Seth Forshee wrote:
> > Unpriveleged containers cannot run mknod, making it difficult to support
> > devices which appear at runtime.
> Wait.
> Why would you even want a container to see a "ne
Hi,
I'm looking to use roundup_pow_of_two() (actually, order_base_2())
from , but it seems that it only supports 64-bit integers
if your toolchain uses a 64-bit 'unsigned long' type. This is strange,
considering that ilog2() is explicitly designed for 32-bit or 64-bit
compatibility.
I also note t
On Tue, May 13, 2014 at 10:54:58AM +0200, Vlastimil Babka wrote:
> On 05/13/2014 02:44 AM, Joonsoo Kim wrote:
> >On Mon, May 12, 2014 at 04:15:11PM +0200, Vlastimil Babka wrote:
> >>Compaction uses compact_checklock_irqsave() function to periodically check
> >>for
> >>lock contention and need_resc
On Thu, May 15, 2014 at 07:54:57AM +1000, Dave Chinner wrote:
> On Tue, May 13, 2014 at 08:31:02PM +0200, Mateusz Guzik wrote:
> > This helps hang troubleshooting efforts when only dmesg is available.
>
> I really don't think that spamming dmesg every time a filesystem is
> frozen or thawed is a g
> Now we define MAX_PHYSMEM_BITS and SECTION_SIZE_BITS as
> macros. So if we deal with vmcores with different values
> of these two macros. We have to recompile makedumpfile.
There are other macros which have architecture-specific values
(e.g. __PAGE_OFFSET), and some fun
On Wed, May 14, 2014 at 03:14:30PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > On Fri, May 09, 2014 at 02:39:20PM +0200, Marek Szyprowski wrote:
> >> Hello,
> >>
> >> On 2014-05-08 02:32, Joonsoo Kim wrote:
> >> >This series tries to improve CMA.
> >> >
> >> >CMA is introduced to
H. Peter Anvin wrote:
> Seems to me to make the code easier to read, not harder. That was the
> whole point.
I thought it made it harder by moving the terminating 1 bit out of the
driver proper, where it has a symbolic name. Thus someone comparing
the driver to the spec has to read another source
On Wed, May 14, 2014 at 02:12:19PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > CMA is introduced to provide physically contiguous pages at runtime.
> > For this purpose, it reserves memory at boot time. Although it reserve
> > memory, this reserved memory can be used for movable me
On Tue, May 13, 2014 at 12:00:57PM +0900, Minchan Kim wrote:
> Hey Joonsoo,
>
> On Thu, May 08, 2014 at 09:32:23AM +0900, Joonsoo Kim wrote:
> > CMA is introduced to provide physically contiguous pages at runtime.
> > For this purpose, it reserves memory at boot time. Although it reserve
> > memor
Am 14.05.2014 21:24, schrieb Alexander Holler:
> Am 14.05.2014 21:06, schrieb Rob Herring:
>> I still have not seen an example of A depends on B, deferred probe
>> fails because of ? and here is the code for A that works around the
>> problem.
>>
>>> Anyway, this feature is totally independ of the
On Wed, 2014-04-02 at 16:54 +0800, Gui Hecheng wrote:
> For modern filesystems such as btrfs, t/p/e size level operations
> are common.
> add size unit t/p/e parsing to memparse
>
> Signed-off-by: Gui Hecheng
> ---
> changelog
> v1->v2: replace kilobyte with kibibyte, and others
> v2-
On 05/09/2014 05:31 PM, Guenter Roeck wrote:
The watchdog subsystem provides an API to perform a system reboot.
Use it.
With this change, the arm_pm_restart callback is now optional,
so check if it is set before calling it.
Tested-by: Jonas Jensen
Signed-off-by: Guenter Roeck
Any comments /
On 05/09/2014 05:31 PM, Guenter Roeck wrote:
The watchdog subsystem provides an API to perform a system reboot.
Use it.
Signed-off-by: Guenter Roeck
Any comments / Ack from the arm maintainers ?
Thanks,
Guenter
---
v2: No change
arch/arm64/kernel/process.c | 3 +++
1 file changed, 3 in
On Wed, May 14, 2014 at 04:34:48PM -0500, Seth Forshee wrote:
> Unpriveleged containers cannot run mknod, making it difficult to support
> devices which appear at runtime.
Wait.
Why would you even want a container to see a "new" device? That's the
whole point, your container should see a "clean"
Seems to me to make the code easier to read, not harder. That was the whole
point.
On May 14, 2014 6:15:51 PM PDT, George Spelvin wrote:
>H. Peter Anvin wrote:
>> If the whole point of this is to use it for MMC/SD cards, why not
>just
>> also subsume the OR 1 and call it crc7_mmc() or something
H. Peter Anvin wrote:
> If the whole point of this is to use it for MMC/SD cards, why not just
> also subsume the OR 1 and call it crc7_mmc() or something like that.
>
> (Which I'm all for doing... I don't know of any other crc7 users.)
You'll find all users in my patch series. 2/3 updates the MM
op 14-05-14 17:29, Christian König schreef:
+/* did fence get signaled after we enabled the sw irq? */
+if (atomic64_read(&fence->rdev->fence_drv[fence->ring].last_seq) >=
fence->seq) {
+radeon_irq_kms_sw_irq_put(fence->rdev, fence->ring);
+return false;
+}
+
+fen
Good Day,
my name is Langat John from Kenya Nairobi I work with Kenya
commercial Bank every quarter we carry out checks on clients bank
accounts.Twelve years ago I realise a strange bank account with an enormos sum
of $75.000.000 USD. The amount did not baffle me, but what pulled my
On 05/14/2014 05:35 PM, Andy Lutomirski wrote:
>>
>> More fundamentally, futex(2), like clone(2), are things that can be
>> legitimately by user space without automatically breaking all of glibc.
>
> I'm lost -- I think the missing verb is important :)
>
... legitimately *used* by user space ...
On 05/11/2014 03:02 AM, George Spelvin wrote:
> From 770aa22e6c9c92027e3e21797192ccabb3e7c70e Mon Sep 17 00:00:00 2001
> From: George Spelvin
> Date: Sat, 10 May 2014 10:32:57 -0400
> Subject: [PATCH v2 1/3] lib/crc7: Shift crc7() output left 1 bit
>
> This eliminates a 1-bit left shift in every
On Wed, May 14, 2014 at 5:28 PM, H. Peter Anvin wrote:
> On 05/14/2014 01:56 PM, Davidlohr Bueso wrote:
>>>
However, unless I'm sorely mistaken, the larger problem is that glibc
removed the futex() call entirely, so these man pages don't describe
>>>
>>> I don't think futex() ever was in
Currently the Tegra1x4 clock init code hard-codes the mux setting
for xusb_hs_src and treats it as a fixed-factor clock. It is,
however, a mux which can be parented by either xusb_ss_src/2 or
pll_u_60M. Add the fixed-factor clock xusb_ss_div2 and put an
entry in periph_clks[] for the xusb_hs_src
From: Jim Lin
The parent-to-index mapping for xusb_fs_src is incorrect.
Fix it by adding a mux table.
Signed-off-by: Jim Lin
Signed-off-by: Andrew Bresticker
---
drivers/clk/tegra/clk-tegra-periph.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/tegra/clk-t
Initialize the XUSB-related clocks with appropriate parents and rates
for both Tegra114 and Tegra124.
Signed-off-by: Jim Lin
Signed-off-by: Andrew Bresticker
---
drivers/clk/tegra/clk-tegra114.c | 7 ++-
drivers/clk/tegra/clk-tegra124.c | 6 ++
2 files changed, 12 insertions(+), 1 delet
On 05/13/2014 01:17 PM, Helge Deller wrote:
>
> We can't use CONFIG_64BIT for a userspace header file. Please use
> #if !defined(__LP64__)
> instead.
> But even then I'm not sure if it's all correct...
>
__u64 (or __s64) works fine in that case.
-hpa
--
To unsubscribe from this list:
Enable the XHCI host controller and XUSB PHY on Venice2. All three
USB2.0 ports are owned by the XHCI controller and the two SuperSpeed
ports are mapped to the external USB2.0 ports.
Signed-off-by: Andrew Bresticker
---
arch/arm/boot/dts/tegra124-venice2.dts | 46 ++-
From: Jim Lin
Enable hardware control of PLLE spread-spectrum, IDDQ, and enable
controls when enabling PLLE. The hardware (e.g. XUSB) using PLLE
will use these controls for power-saving optimizations.
Signed-off-by: Jim Lin
Signed-off-by: Andrew Bresticker
---
drivers/clk/tegra/clk-pll.c | 3
Board-specific USB configuration data is stored in FUSE_SKU_CALIB_0.
Export a function to read it so the PHY can be properly configured.
Signed-off-by: Andrew Bresticker
---
arch/arm/mach-tegra/fuse.c | 13 +
include/linux/tegra-soc.h | 1 +
2 files changed, 14 insertions(+)
diff
The XUSB PHY driver will be accessing the CAR registers through the
syscon interface.
Signed-off-by: Andrew Bresticker
---
arch/arm/boot/dts/tegra124.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra124.dtsi b/arch/arm/boot/dts/tegra124.dtsi
index 1
Add support for the on-chip XHCI host controller present on NVIDIA
Tegra114 and later SoCs.
The driver is currently very basic: it loads the controller with its
firmware, starts the controller, and is able to service messages sent
by the controller's firmware. The hardware supports device mode as
And nodes for the XHCI host controller and XUSB PHY present on Tegra124.
Signed-off-by: Andrew Bresticker
---
arch/arm/boot/dts/tegra124.dtsi | 37 +
1 file changed, 37 insertions(+)
diff --git a/arch/arm/boot/dts/tegra124.dtsi b/arch/arm/boot/dts/tegra124.dt
Add support for the Tegra XUSB PHY present on Tegra114 and Tegra124 SoCs.
This provides all PHY functionality for the Tegra XHCI host-controller
driver and supports UTMI, HSIC, and SuperSpeed interfaces.
While this PHY driver currently only handles USB, the SATA and PCIe
PHYs are programmed in a s
This is a first pass at the host and PHY drivers necessary for USB3.0
support on Tegra114 and Tegra124. The Tegra XHCI host controller requires
external firmware [1] which must be loaded before using any USB ports owned
by the controller. The XUSB PHY driver handles mapping and enabling of
the UT
Pavel Machek wrote;
> On Sun 2014-05-11 05:16:07, George Spelvin wrote:
>> To do it properly, I have to rename all of:
>>
>> crc7_syndrome_table[]
>> crc7_byte()
>> crc7()
>>
>> even though the third is the only (in-tree) user of the first two.
> If the first two are static, there's no problem.
On 05/14/2014 01:56 PM, Davidlohr Bueso wrote:
>>
>>> However, unless I'm sorely mistaken, the larger problem is that glibc
>>> removed the futex() call entirely, so these man pages don't describe
>>
>> I don't think futex() ever was in glibc--that's by design, and
>> completely understandable: no
On 05/14/2014 09:18 AM, Darren Hart wrote:
>
> However, unless I'm sorely mistaken, the larger problem is that glibc
> removed the futex() call entirely, so these man pages don't describe
> something users even have access to anymore. I had to revert to calling
> the syscalls directly in the futex
On 05/14/2014 02:33 PM, John Stultz wrote:
>
> We can do some tricks for internal optimizations here if these are
> critical. I'd be more concerned about userland divisions where moving
> to a 64bit time_t would cause performance issues that we cannot help
> optimize.
>
Honestly, the cost of no
* Arnd Bergmann [140514 11:16]:
> On Wednesday 14 May 2014 10:39:31 Greg KH wrote:
> > On Tue, May 13, 2014 at 09:27:33AM -0700, Tony Lindgren wrote:
> > > * Arnd Bergmann [140513 08:13]:
> > >
> > > I did not look what percentage has tristate in the Kconfig,
> > > but that might keep some peopl
Fixed indenting of if statement in socklnd.c to meet kernel coding style.
Signed-off-by: Masaru Nomura
---
.../staging/lustre/lnet/klnds/socklnd/socklnd.c|3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c
b/drivers/st
On Wed, 14 May 2014, Chris Metcalf wrote:
> On 5/7/2014 7:15 PM, Thomas Gleixner wrote:
> > On Wed, 7 May 2014, Chris Metcalf wrote:
> > > We have an internal change that we haven't upstreamed yet that makes
> > > irqs actually (cpu,ipi) pairs, so that more irqs can be allocated.
> > > As a result
Added a required space before open brace and parenthsis
in socklnd.c to meet kernel coding style.
Signed-off-by: Masaru Nomura
---
.../staging/lustre/lnet/klnds/socklnd/socklnd.c|4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lnet/klnds/sockl
On Wed, 14 May 2014, Chris Metcalf wrote:
> On 5/7/2014 11:44 AM, Thomas Gleixner wrote:
> > We want to convert the drivers over to the new interface and finally
> > tile to sparse irqs. Implement irq_alloc/free_hwirq() for step by step
> > migration.
> >
> >
> > +void irq_free_hwirq(unsigned int
On Wed, 14 May 2014, Chris Metcalf wrote:
> On 5/7/2014 11:44 AM, Thomas Gleixner wrote:
> > --- tip.orig/kernel/irq/Kconfig
> > +++ tip/kernel/irq/Kconfig
> > @@ -17,6 +17,11 @@ config GENERIC_IRQ_SHOW
> > config GENERIC_IRQ_SHOW_LEVEL
> > bool
> > +# Facility to allocate an hardware
The oops can be triggered in qemu using -no-hpet (but not nohpet) by
reading a couple of pages past the end of the vdso text. This
should send SIGBUS instead of OOPSing.
The bug was introduced by:
commit 7a59ed415f5b57469e22e41fc4188d5399e0b194
Author: Stefani Seibold
Date: Mon Mar 17 23:22:0
On Wed, 2014-04-23 at 16:30 +0300, Dmitry Kasatkin wrote:
> This patch provides functionality to replace the IMA policy at runtime.
>
> By default, the IMA policy can be successfully updated only once,
> but with this patch when the kernel configuration option
> CONFIG_IMA_POLICY_REPLACEABLE is e
Commit-ID: fa81511bb0bbb2b1aace3695ce869da9762624ff
Gitweb: http://git.kernel.org/tip/fa81511bb0bbb2b1aace3695ce869da9762624ff
Author: Linus Torvalds
AuthorDate: Wed, 14 May 2014 16:33:54 -0700
Committer: H. Peter Anvin
CommitDate: Wed, 14 May 2014 16:33:54 -0700
x86-64, modify_ldt: Ma
Hi Alex
On Fri, May 9, 2014 at 11:28 PM, Alex Williamson
wrote:
>
>
> Original description:
>
> This series attempts to fix a couple issues we've had outstanding in
> the PCI/IOMMU code for a while. The first issue is with devices that
> use the wrong requester ID for DMA transactions. We
On Wed, 14 May 2014, Carlos O'Donell wrote:
> On 05/14/2014 03:03 PM, Michael Kerrisk (man-pages) wrote:
> >> However, unless I'm sorely mistaken, the larger problem is that glibc
> >> removed the futex() call entirely, so these man pages don't describe
> >
> > I don't think futex() ever was in g
The debug controller, as its name suggests, exposes cgroup core
internals to userland to aid debugging. Unfortunately, except for the
name, there's no provision to prevent its usage in production
configurations and the controller is widely enabled and mounted
leaking internal details to userland.
On 05/12/2014 06:21 PM, Santosh Shilimkar wrote:
On Thursday 08 May 2014 06:31 PM, Ivan Khoronzhuk wrote:
From: Sandeep Paulraj
It is needed for k2l keystone2 EVM which uses NAND flash with 4K page
size, hence add support for 4K page size nand devices.
Signed-off-by: Sandeep Paulraj
Signed-
The oops can be triggered in qemu using -no-hpet (but not nohpet) by
running a 32-bit program and reading a couple of pages before the vdso.
This should send SIGBUS instead of OOPSing.
The bug was introduced by:
commit 7a59ed415f5b57469e22e41fc4188d5399e0b194
Author: Stefani Seibold
Date: Mon
On Wed, May 14, 2014 at 4:16 PM, Andrew Morton
wrote:
> On Wed, 14 May 2014 16:01:22 -0700 Andy Lutomirski
> wrote:
>
>> The access should fail, but it shouldn't oops.
>>
>> Signed-off-by: Andy Lutomirski
>> ---
>>
>> The oops can be triggered in qemu using -no-hpet (but not nohpet) by
>> runni
* Peter Ujfalusi [140513 03:31]:
> dma-channels, ti,edma-regions and ti,edma-slots no longer needed in DT since
> the the same information is available in the IP's CCCFG register.
This too:
Acked-by: Tony Lindgren
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 05/15/2014 12:32 AM, Mike Turquette wrote:
> Quoting Sebastian Hesselbarth (2014-05-11 13:24:35)
>> This adds mandatory device tree binding documentation for the clock related
>> IP found on Marvell Berlin2 (BG2, BG2CD, and BG2Q) SoCs.
>>
>> Signed-off-by: Sebastian Hesselbarth
>> ---
>> Cc: Mi
* Peter Ujfalusi [140513 03:31]:
> dma-channels, ti,edma-regions and ti,edma-slots no longer needed in DT since
> the the same information is available in the IP's CCCFG register.
Sounds like this must go with the edma patches or else
applied later on. Probably best to merge it with edma:
Acked-
On Wed, 14 May 2014 16:01:22 -0700 Andy Lutomirski wrote:
> The access should fail, but it shouldn't oops.
>
> Signed-off-by: Andy Lutomirski
> ---
>
> The oops can be triggered in qemu using -no-hpet (but not nohpet) by
> running a 32-bit program and reading a couple of pages before the vdso.
* Mugunthan V N [140513 01:45]:
> Add AM437x GP EVM cpsw device tree node
>
> Mugunthan V N (2):
> ARM: dts: am4372: Add cpsw phy sel dt node
> ARM: dts: am437x-gp-evm: Add ethernet support for GP EVM
Thanks applying both into omap-for-v3.16/dt.
Tony
--
To unsubscribe from this list: send t
On Wed, 14 May 2014, Christoph Lameter wrote:
> - Shepherd thread as a general worker thread. This means
> that the general mechanism to control worker thread
> cpu proposed by Frederic Weisbecker is necessary to
> restrict the shepherd thread to the cpus not used
> for low latency tasks. H
* Mugunthan V N [140513 01:54]:
> Tony/Benoit
>
> On Tuesday 13 May 2014 01:34 PM, Mugunthan V N wrote:
> > Adding device tree entry for CPSW to make it work in Dual EMAC mode.
> >
> > DRA7 cpsw phy sel driver patch has been pulled in net-next git with the
> > following commit id *d415fa1b88748d6
On Wed, 14 May 2014, Carlos O'Donell wrote:
> On 05/14/2014 05:22 AM, Peter Zijlstra wrote:
> >>> I believe the thinking goes that if we get to here, then the lock is in an
> >>> inconsistent state (between kernel and userspace). I don't have an answer
> >>> for
> >>> why pausing forever would be
The access should fail, but it shouldn't oops.
Reported-by: Sasha Levin
Signed-off-by: Andy Lutomirski
---
This applies to tip/x86/vdso and should be applied to unbreak Trinity
on linux-next.
arch/x86/vdso/vma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/v
The access should fail, but it shouldn't oops.
Signed-off-by: Andy Lutomirski
---
The oops can be triggered in qemu using -no-hpet (but not nohpet) by
running a 32-bit program and reading a couple of pages before the vdso.
This will conflict with tip/x86/vdso. Sorry.
arch/x86/vdso/vdso32-set
Am 14.05.2014 21:06, schrieb Rob Herring:
> On Wed, May 14, 2014 at 12:45 PM, Alexander Holler
> wrote:
>> Am 14.05.2014 19:30, schrieb Rob Herring:
>>
>>> On Wed, May 14, 2014 at 11:23 AM, Alexander Holler
>>> wrote:
Am 14.05.2014 18:05, schrieb Grant Likely:
> On Wed, May 14
On Wed, 14 May 2014 16:18:51 +0800 Richard Lee wrote:
> For the IO mapping, the same physical address space maybe
> mapped more than one time, for example, in some SoCs:
> - 0x20001000 ~ 0x20001400 --> 1KB for Dev1
> - 0x20001400 ~ 0x20001800 --> 1KB for Dev2
> and the page size is 4KB.
>
On Wed, 14 May 2014, Carlos O'Donell wrote:
> On 05/14/2014 06:26 AM, Thomas Gleixner wrote:
> > On Wed, 14 May 2014, Carlos O'Donell wrote:
> >> On 05/13/2014 05:08 AM, Thomas Gleixner wrote:
> >>> So anything else than ESRCH and EDEADLK is ignored and then the thing
> >>> happily returns 0 at the
On Wed, May 14, 2014 at 2:31 PM, Andrew Morton
wrote:
> On Wed, 14 May 2014 17:11:00 -0400 Sasha Levin wrote:
>
>> > In my linux-next all that code got deleted by Andy's "x86, vdso:
>> > Reimplement vdso.so preparation in build-time C" anyway. What kernel
>> > were you looking at?
>>
>> Deleted?
Hi Jean,
On Wed, May 14, 2014 at 12:23 PM, Jean Delvare wrote:
> Hi Mike,
>
> On Wed, 14 May 2014 08:52:36 -0700, Mike Waychison wrote:
>> On Wed, May 14, 2014 at 2:23 AM, Jean Delvare wrote:
>> > Sorry for joining the party a little late but I am just discovering the
>> > dmi-sysfs kernel modul
David,
On Tue, May 6, 2014 at 5:12 PM, David Riley wrote:
> This script makes use of the udelay_test module to exercise udelay()
> and ensure that it is delaying long enough (as compared to ktime).
>
> Signed-off-by: David Riley
> ---
> tools/time/udelay_test.sh | 66
> ++
On 5/14/14, 5:37 PM, Dave Chinner wrote:
> On Thu, May 15, 2014 at 08:00:52AM +1000, Dave Chinner wrote:
>> On Wed, May 14, 2014 at 01:39:45PM +0200, Jan Kara wrote:
>>> On Wed 14-05-14 13:26:21, Mateusz Guzik wrote:
On Wed, May 14, 2014 at 01:14:49PM +0200, Jan Kara wrote:
> On Wed 14-05-
Quoting Boris BREZILLON (2014-05-14 00:30:59)
> Hello Mike,
>
> On 14/05/2014 02:51, Mike Turquette wrote:
> > Quoting Boris BREZILLON (2014-05-09 04:11:49)
> >> +struct clk_ops ar100_ops = {
> >> + .recalc_rate = ar100_recalc_rate,
> >> + .determine_rate = ar100_determine_rate,
> >> +
On Thu, May 15, 2014 at 08:00:52AM +1000, Dave Chinner wrote:
> On Wed, May 14, 2014 at 01:39:45PM +0200, Jan Kara wrote:
> > On Wed 14-05-14 13:26:21, Mateusz Guzik wrote:
> > > On Wed, May 14, 2014 at 01:14:49PM +0200, Jan Kara wrote:
> > > > On Wed 14-05-14 00:04:43, Mateusz Guzik wrote:
> > > >
On Wed, 14 May 2014, Tony Battersby wrote:
> Hugh Dickins wrote:
> > Checking page counts in a GB file prior to sealing does not appeal at
> > all: we'd be lucky ever to find them all accounted for.
>
> Here is a refinement of that idea: during a seal operation, iterate over
> all the pages in the
On Wed, May 14, 2014 at 07:10:51PM +0200, Peter Zijlstra wrote:
> On Wed, May 14, 2014 at 01:02:38PM -0400, Tejun Heo wrote:
> > On Wed, May 14, 2014 at 04:00:34PM +0200, Peter Zijlstra wrote:
> > > Does something like the below help any? I noticed those things (cpudl
> > > and cpupri) had [NR_CPUS
Round clock frequencies to the nearest possible frequency. As opposed to
the nearest that does not exceed the requested one.
Signed-off-by: Soren Brinkmann
---
drivers/cpufreq/cpufreq-cpu0.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/d
When matching a frequency against the freq_table, allow small deviances to
allow rounding errors. Rounding errors are likely to occur due to the
differenct frequency resolutions used in the common clock vs cpufreq
frameworks.
Signed-off-by: Soren Brinkmann
---
drivers/cpufreq/cpufreq_stats.c |
Introduce a new API function to round a rate to the closest possible
rate the HW clock can generate.
In contrast to 'clk_round_rate()' which works similar, but always returns
a frequency <= its input rate.
The code comes from Uwe and was copied from this LKML thread:
https://lkml.org/lkml/2013/3/2
Some issues in regards to rounding and different frequency resolution in
the cpufreq and common clock frameworks have been resolved and allow
specifying Zynq's OPPs with properly rounded values.
Signed-off-by: Soren Brinkmann
---
arch/arm/boot/dts/zynq-7000.dtsi | 4 ++--
1 file changed, 2 inse
The current way of rounding clock frequencies always rounds down and
doesn't allow deviations above the requested frequency. For the Ethernet
case though, it is more important to minimize deviations than not
exceeding the requested frequency.
Signed-off-by: Soren Brinkmann
---
---
drivers/net/e
Hi,
I have one or two problems with cpufreq and the CCF, which are caused by
rounding/different frequency resolutions.
cpufreq works with kHz, while the CCF uses Hz. On Zynq our default frequency is
6 Hz which the CCF, due to rounding, reports as 0. And for
cpufreq, which simply d
Quoting Sebastian Hesselbarth (2014-05-11 13:24:35)
> This adds mandatory device tree binding documentation for the clock related
> IP found on Marvell Berlin2 (BG2, BG2CD, and BG2Q) SoCs.
>
> Signed-off-by: Sebastian Hesselbarth
> ---
> Cc: Mike Turquette
> Cc: Rob Herring
> Cc: Pawel Moll
>
This script makes use of the udelay_test module to exercise udelay()
and ensure that it is delaying long enough (as compared to ktime).
Signed-off-by: David Riley
---
tools/time/udelay_test.sh | 66 +
1 file changed, 66 insertions(+)
create mode 100
This change adds a module and a script that makes use of it to
validate that udelay delays for at least as long as requested
(as compared to ktime).
Changes since v1:
- allow udelay() to be 0.5% faster than requested as per feedback
David Riley (2):
kernel: time: Add udelay_test module to valid
Create a module that allows udelay() to be executed to ensure that
it is delaying at least as long as requested (with a little bit of
error allowed).
Signed-off-by: David Riley
Reviewed-by: Doug Anderson
---
kernel/time/Kconfig |7 ++
kernel/time/Makefile |1 +
kernel/time/ud
On Wed, 14 May 2014 07:52:38 -0700 Davidlohr Bueso wrote:
> > --- a/ipc/sem.c
> > +++ b/ipc/sem.c
> > @@ -993,38 +993,33 @@ static void do_smart_update(struct sem_array *sma,
> > struct sembuf *sops, int nsop
> > }
> >
> > /*
> > - * check_qop: Test how often a queued operation sleeps on the
On Thu 15-05-14 00:08:34, Richard Weinberger wrote:
> On Thu, May 15, 2014 at 12:01 AM, Jan Kara wrote:
> > On Sat 03-05-14 22:33:24, Fabian Frederick wrote:
> >> __constant_cpu_to_le32 converted to cpu_to_le32
> >>
> >> Cc: reiserfs-de...@vger.kernel.org
> >> Cc: Andrew Morton
> >> Signed-off-by
On Thu, 2014-05-15 at 00:08 +0200, Richard Weinberger wrote:
> On Thu, May 15, 2014 at 12:01 AM, Jan Kara wrote:
> > On Sat 03-05-14 22:33:24, Fabian Frederick wrote:
> >> __constant_cpu_to_le32 converted to cpu_to_le32
> >>
> >> Cc: reiserfs-de...@vger.kernel.org
> >> Cc: Andrew Morton
> >> Sign
On Wed, 14 May 2014 23:43:36 +0200
abdoulaye berthe wrote:
> this fixes a compilation warning by checking
> the retun value of gpiochip_remove()
Really, I would rather change the gpiochip_remove return type to void.
What is the point of printing a useless error message in case
of a failure and
101 - 200 of 936 matches
Mail list logo
