Since zram has no control feature to limit memory usage,
it makes hard to manage system memrory.
This patch adds new knob "mem_limit" via sysfs to set up the
a limit so that zram could fail allocation once it reaches
the limit.
Signed-off-by: Minchan Kim
---
zs_get_total_size_bytes returns a amount of memory zsmalloc
consumed with *byte unit* but zsmalloc operates *page unit*
rather than byte unit so let's change the API so benefit
we could get is that reduce unnecessary overhead
(ie, change page unit with byte unit) in zsmalloc.
Now, zswap can
On Mon, Aug 18, 2014 at 11:59:13AM -0400, Pranith Kumar wrote:
> Fix building errors occuring due to a missing export of flush_icache_range()
> in
>
> kisskb.ellerman.id.au/kisskb/buildresult/11677809/
>
> ERROR: "flush_icache_range" [drivers/misc/lkdtm.ko] undefined!
>
> Signed-off-by:
On Wed, Aug 20, 2014 at 03:53:18PM +0900, Minchan Kim wrote:
> On Wed, Aug 20, 2014 at 02:26:50AM -0400, David Horner wrote:
> > On Tue, Aug 19, 2014 at 3:54 AM, Minchan Kim wrote:
> > > Normally, zram user could get maximum memory usage zram consumed
> > > via polling mem_used_total with sysfs
On Wed, Aug 20, 2014 at 07:05:09PM +0400, Konstantin Khlebnikov wrote:
> * move special branch for balloon migraion into migrate_pages
> * remove special mapping for balloon and its flag AS_BALLOON_MAP
> * embed struct balloon_dev_info into struct virtio_balloon
> * cleanup balloon_page_dequeue,
On Wed, Aug 20, 2014 at 05:46:22PM -0400, Peter Feiner wrote:
> In readable+writable+shared VMAs, PTEs created for read faults have
> their write bit set. If the read fault happens after VM_SOFTDIRTY is
> cleared, then the PTE's softdirty bit will remain clear after
> subsequent writes.
>
>
On Wed, Aug 20, 2014 at 07:05:04PM +0400, Konstantin Khlebnikov wrote:
> This patch replaces checking AS_BALLOON_MAP in page->mapping->flags
> with PageBalloon which is stored directly in the struct page.
>
> Signed-off-by: Konstantin Khlebnikov
> ---
> include/linux/balloon_compaction.h | 85
On Wed, Aug 20, 2014 at 07:04:58PM +0400, Konstantin Khlebnikov wrote:
> This patch adds page state PageBallon() and functions __Set/ClearPageBalloon.
> Like PageBuddy() PageBalloon() looks like page-flag but actually this is
> special
> state of page->_mapcount counter. There is no conflict
[Messed up Eric's email address on first send. Resending...]
Hello Eric et al.
With the namespaces changes, a number of additions have been
made to the setns(2) man page, so I will send out the entire page
for review at the same time as the various namespaces page.
The rendered version is
Hello Eric et al.
With the namespaces changes, a number of additions have been
made to the unshare(2) man page, so I will send out the entire page
for review at the same time as the various namespaces page.
The rendered version is below, and the source is attached.
Review comments/suggestions
Hello Eric et al.
With the namespaces changes, a number of additions have been
made to the setns(2) man page, so I will send out the entire page
for review at the same time as the various namespaces page.
The rendered version is below, and the source is attached.
Review comments/suggestions for
Hello Eric et al.
Here is the current draft of the namespaces(7) man page, which
gives an overview of namespaces and the namespaces API. The rendered
version is below, and the source is attached.
Review comments/suggestions for improvements / bug fixes welcome.
Cheers,
Michael
==
NAME
Hello Eric et al.
Here is the current draft of the pid_namespaces(7) man page, which
described PID namespaces. The rendered version is below, and the
source is attached.
Review comments/suggestions for improvements / bug fixes welcome.
Cheers,
Michael
==
NAME
pid_namespaces - overview
Hello Eric et al.,
For various reasons, my work on the namespaces man pages
fell off the table a while back. Nevertheless, the pages have
been close to completion for a while now, and I recently restarted,
in an effort to finish them. As you also noted to me f2f, there have
been recently been
On Wed, Aug 20, 2014 at 07:04:46PM +0400, Konstantin Khlebnikov wrote:
> LRU-lock isn't required for balloon page isolation. This check makes migration
> of some ballooned pages mostly impossible because isolate_migratepages_range()
> drops LRU lock periodically.
>
just for historical/explanatory
On Wed, Aug 20, 2014 at 07:04:40PM +0400, Konstantin Khlebnikov wrote:
> Proper testing shows yet another problem in balloon migration: it works only
> once for each page. balloon_page_movable() check page flags and page_count.
> In __unmap_and_move page is locked, reference counter is elevated,
On Wed, Aug 20, 2014 at 07:04:35PM +0400, Konstantin Khlebnikov wrote:
> Sasha Levin reported KASAN splash inside isolate_migratepages_range().
> Problem is in function __is_movable_balloon_page() which tests AS_BALLOON_MAP
> in page->mapping->flags. This function has no protection against
On Tue, 10 Jun 2014, Jiri Kosina wrote:
> We have been chasing a memory corruption bug, which turned out to be
> caused by very old gcc (4.3.4), which happily turned conditional load into
> a non-conditional one, and that broke correctness (the condition was met
> only if lock was held) and
On Wed, Aug 20, 2014 at 12:20 AM, Eric W. Biederman
wrote:
> Cong Wang writes:
>
>> I saw the following kernel warning:
>
> Cong thanks for finding and tracking this. I was clearly asleep at the
> switch when I was testing my fix to the nfs client code :(
>
> I have applied this patch and will
From: Douglas Lehr
The Crocodile chip occasionally comes up with 4k and 8k BAR sizes.
Due to an errata, setting the SR-IOV page size causes the physical
function BARs to expand to the system page size. Since ppc64 uses
64k pages, when Linux tries to assign the smaller resource sizes
to the now
On Tue, Aug 12, 2014 at 11:27:35AM -0500, Shawn Bohrer wrote:
> From: Shawn Bohrer
>
> In debugging an application that receives -ENOMEM from ib_reg_mr() I
> found that ib_umem_get() can fail because the pinned_vm count has
> wrapped causing it to always be larger than the lock limit even with
>
On Wed, Aug 20, 2014 at 1:24 AM, Christian Kujau wrote:
> On Tue, 19 Aug 2014 at 21:20, Eric W. Biederman wrote:
>
>> Cong Wang writes:
>>
>> > I saw the following kernel warning:
>>
>> Cong thanks for finding and tracking this. I was clearly asleep at the
>> switch when I was testing my fix to
On Tue, 2014-08-19 at 23:06 -0400, Xiong Zhou wrote:
> When export root dir(/) via nfs, and mount a particular dir under root, eg
> /nfsexport, there will be defect double slash output in /proc/mounts, like
> localhost://nfsexport.
>
> Signed-off-by: Xiong Zhou
> ---
> fs/nfs/super.c | 2 +-
>
On Wed, 2014-08-20 at 22:17 +, Woodhouse, David wrote:
>
> Except that in the failure case we *free* the old mk->mp and never free
> mk->mp->grp.attrs so it *is* indeed lost.
>
> A simpler version of Arjun's patch might look like this:
>
> diff --git a/kernel/params.c b/kernel/params.c
>
On Mon 11 Aug 08:40 PDT 2014, Ivan T. Ivanov wrote:
> diff --git a/arch/arm/boot/dts/qcom-apq8074-dragonboard-pmics-pins.dtsi
> b/arch/arm/boot/dts/qcom-apq8074-dragonboard-pmics-pins.dtsi
[...]
> +
> +_gpios {
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <_gpios_default>;
> +
> +
On Mon, Aug 18, 2014 at 05:29:26PM +0800, Hanjun Guo wrote:
> On 2014-8-15 18:01, Catalin Marinas wrote:
> > Hanjun,
>
> Hi Catalin,
>
> >
> > On Fri, Aug 15, 2014 at 10:09:42AM +0100, Hanjun Guo wrote:
> >> On 2014-8-14 18:27, Catalin Marinas wrote:
> >>> On Thu, Aug 14, 2014 at 04:21:25AM
On Wed, Aug 20, 2014 at 7:31 AM, Liviu Dudau wrote:
> On Wed, Aug 20, 2014 at 01:27:57PM +0200, Arnd Bergmann wrote:
>> On Tuesday 12 August 2014, Liviu Dudau wrote:
>> > + return of_create_pci_host_bridge(dev, 0, 0xff, _pci_ops,
>> > + gen_pci_setup,
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
to get udf, isofs, and ext3 bug fix.
Top of the tree is e6d8fb340f20. The full shortlog is:
Chao Yu (1):
udf: avoid unneeded up_write when fail to add entry in ->symlink
On Wed, Aug 20, 2014 at 04:33:29PM +0530, Sreekanth Reddy wrote:
> HI,
>
>
>
> For SRIOV support, currently in the KVM environment, mpt3sas driver can use
> the API pci_vfs_assigned() to know the number of VFs that are currently
> assigned to the running VMs. So that during the PF driver unload
On Mon 11 Aug 08:40 PDT 2014, Ivan T. Ivanov wrote:
[...]
> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
> b/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
[...]
> +SUBNODES:
[...]
> +- function:
> + Usage: required
> + Value type:
> +
On Wed, Aug 20, 2014 at 7:17 PM, Mark Einon wrote:
> do {
> pci_read_config_dword(pdev,
> - LBCIF_DATA_REGISTER, );
> + LBCIF_DATA_REGISTER,
> +
i2c_wack is only used to implement a while(1) loop, so let's remove it.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/et131x/et131x.c b/drivers/staging/et131x/et131x.c
index
There's already working code to set the mac address, so let's use it.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 53 +
1 file changed, 1 insertion(+), 52 deletions(-)
diff --git a/drivers/staging/et131x/et131x.c
Replace a long list of contiguous writel() calls with a for loop iterating
over the same address values.
Also remove redundant comments on the macstat registers, the variable names
are good enough.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 59 +++--
There's no need to handle any rx/tx interrupts in the middle of an mtu
change, so don't.
After this change, receive and transmit interrupts are only handled in
one place, which paves the way to using NAPI.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 2 --
1 file changed, 2
Replace a long list of contiguous writel() calls with a for loop iterating
over the same values.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 27 +++
1 file changed, 3 insertions(+), 24 deletions(-)
diff --git a/drivers/staging/et131x/et131x.c
We actually mean to clear the ET_INTR_TXDMA_ISR reg after handling
a completed transfer, not the ET_INTR_TXDMA_ERR reg, which should
get handled immediately after.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
To better describe it's use as a hard limit.
Signed-off-by: Mark Einon
---
drivers/staging/et131x/et131x.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/et131x/et131x.c b/drivers/staging/et131x/et131x.c
index 551b250..df83ea3 100644
---
Let's put a NAPI on this baby...
NAPI support was identified by Dave Miller as a
must to get this driver out of staging. This patchset first tidies up
the code enough to make adding NAPI easier, and the final patch mostly
adds the 'boilerplate' NAPI code as described by:
This implements NAPI support for et131x by:
-adding a napi_struct to the private adapter struct
-changing netfif_rx_skb() call to netif_receive_skb()
-changing et131x_handle_recv_interrupt() to et131x_handle_recv_pkts()
and taking a budget allocation.
-changing et131x_handle_send_interrupt() to
On Thu, 2014-08-21 at 07:35 +0930, Rusty Russell wrote:
>
> Above this:
> if (!mk->mp) {
> num = 0;
> attrs = NULL;
> } else {
> num = mk->mp->num;
> attrs = mk->mp->grp.attrs;
> }
>
> So, attrs is just a
On Wed, Aug 20, 2014 at 2:28 PM, Bjorn Andersson
wrote:
> On Wed 20 Aug 01:06 PDT 2014, Srinivas Kandagatla wrote:
>> 2> Looking back at v3.4 kernel, for gpio modes, BIT(0) of bank 0 is set
>> to enable gpio mode. without this bit driver does not work for output pins.
>>
>
> Thanks, I missed
On Mon 18 Aug 00:16 PDT 2014, Ivan T. Ivanov wrote:
> On Sat, 2014-08-16 at 16:24 +0100, Daniel wrote:
> > @Ivan: sorry about the double post.
> >
> > Am 11.08.2014 um 16:40 schrieb Ivan T. Ivanov :
[...]
> > > +#define PMIC_GPIO_PULL_UP_30 1
> > > +#define PMIC_GPIO_PULL_UP_1P5
Arjun Sreedharan writes:
> On 21 August 2014 02:19, Rusty Russell wrote:
>> Arjun Sreedharan writes:
>>> Do not leak memory when attrs is non NULL and
>>> krealloc() fails. Without temporary variable,
>>> reference to it is lost.
>>>
>>> Signed-off-by: Arjun Sreedharan
>>
>> ...
>>
>>> }
On 08/19/2014 08:17 AM, Mathias Nyman wrote:
> When we manually need to move the TR dequeue pointer we need to set the
> correct cycle bit as well. Previously we used the trb pointer from the
> last event received as a base, but this was changed in
> commit 1f81b6d22a59 ("usb: xhci: Prefer
On Wed 20-08-14 11:38:10, Gioh Kim wrote:
>
> @@ -1381,12 +1383,7 @@ EXPORT_SYMBOL(__find_get_block);
> struct buffer_head *
> __getblk(struct block_device *bdev, sector_t block, unsigned size)
> {
> - struct buffer_head *bh = __find_get_block(bdev, block, size);
>
Chris,
On Tue, Aug 19, 2014 at 8:40 PM, Chris Zhong wrote:
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v2: None
>
> drivers/clk/Kconfig |9 +++
> drivers/clk/Makefile|1 +
> drivers/clk/clk-rk808.c | 146
> +++
> 3 files
On 08/20/2014 07:21 AM, Jan Beulich wrote:
>
> But you're aware that for the last two major releases Xen hasn't been
> supporting
> 32-bit CPUs at all anymore? I.e. why should we limit functionality under Xen
> based on errata on 64-bit-incapable CPUs?
>
Because there is no fscking way we're
On 08/20/2014 07:05 AM, One Thousand Gnomes wrote:
> Doing this stuff for Xen also IMHO makes no sense at all. We shouldn't
> have a kernel full of crap to deal with Xen-isms.
We already *have* a kernel full of crap to deal with Xen-isms. We
screwed that pooch some 10 years ago.
> IFF it means
Chris,
On Tue, Aug 19, 2014 at 8:31 PM, Chris Zhong wrote:
> The RK808 chip is a power management IC for multimedia and handheld
> devices. It contains the following components:
>
> - Regulators
> - RTC
>
> The rk808 core driver is registered as a platform driver and provides
> communication
On Wed 2014-08-20 17:12:42, valdis.kletni...@vt.edu wrote:
> (Adding Al Viro and linux-fsdevel, dropping Mark Brown and the SPI list,
> because this is
> heading off in a different direction now)
>
> On Wed, 20 Aug 2014 22:26:02 +0200, Pavel Machek said:
> > On Wed 2014-08-06 14:27:20,
In readable+writable+shared VMAs, PTEs created for read faults have
their write bit set. If the read fault happens after VM_SOFTDIRTY is
cleared, then the PTE's softdirty bit will remain clear after
subsequent writes.
Here's a simple code snippet to demonstrate the bug:
char* m = mmap(NULL,
On Thu, 2014-08-21 at 06:19 +0930, Rusty Russell wrote:
> Arjun Sreedharan writes:
> > Do not leak memory when attrs is non NULL and
> > krealloc() fails. Without temporary variable,
> > reference to it is lost.
> >
> > Signed-off-by: Arjun Sreedharan
>
> ...
>
> > }
> > - /* Despite
Hi,
I would like to ask if somebody is aware of a correct way to change they way
kernel aligns PCI resources. By default it uses minimal alignment of 1 MB.
Due to the hardware limitation I would need to change that down to 64 kB. With
this change PCI Endpoints with many small BARs would fit
On Wed, Aug 20, 2014 at 03:26:46PM -0400, Pranith Kumar wrote:
> Building booke_wdt fails when trying to build as a module as there is no
> early_param() in module. Fix by using module_param() instead of early_param().
>
> Signed-off-by: Pranith Kumar
> CC: Guenter Roeck
Reviewed-by: Guenter
On Wed 20 Aug 01:06 PDT 2014, Srinivas Kandagatla wrote:
> Hi Bjorn,
>
Hi Srinivas,
Thanks for the testing. I'm reworking the driver to incorporate yours, Linus'
and Ivans feedback.
> Two things which I noticed while trying out this driver to drive a reset
> line.
>
> 1> gpio numbering for
checkpatch.pl fix. Use #include instead of
Signed-off-by: Kieron Browne
---
drivers/staging/dgnc/dgnc_tty.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
index 281491a..c844fac 100644
---
(Adding Al Viro and linux-fsdevel, dropping Mark Brown and the SPI list,
because this is
heading off in a different direction now)
On Wed, 20 Aug 2014 22:26:02 +0200, Pavel Machek said:
> On Wed 2014-08-06 14:27:20, valdis.kletni...@vt.edu wrote:
> > On Wed, 06 Aug 2014 13:53:17 -0400, Nick
With closed loop support, the clock rate of the DFLL can be adjusted.
The oscillator itself in the DFLL is a free-running oscillator whose
rate is directly determined the supply voltage. However, the DFLL
module contains logic to compare the DFLL output rate to a fixed
reference clock (51 MHz)
v4 changes:
DFLL:
- fix wrong register accessors used for the DFLL_OUTPUT_CFG register
- I decided to leave the dfll_i2c_{readl,writel} separate since the
correct barrier function still needs to be called
- fix PMIC I2C voltage register address being uninitialized
On Wed, Aug 20, 2014 at 2:05 PM, SeongJae Park wrote:
> On Thu, Aug 21, 2014 at 5:29 AM, Jim Davis wrote:
>> The linux-next wiki at http://linux.f-seidel.de/linux-next/pmwiki has
>> been gone for several months now.
>
> Yes, I can't load the page, too. BTW, wouldn't it be better to add
> Frank
From: Paul Walmsley
The DVCO present in the DFLL IP block has a separate reset line,
exposed via the CAR IP block. This reset line is asserted upon SoC
reset. Unless something (such as the DFLL driver) deasserts this
line, the DVCO will not oscillate, although reads and writes to the
DFLL IP
Tegra CVB tables encode the relationship between operating voltage
and optimal frequency as a function of the so-called speedo value.
The speedo value is written to the on-chip fuses at the factory,
which allows the voltage-frequency operating points to be calculated
on an per-chip basis.
Add
The DFLL clocksource is a separate IP block from the usual
clock-and-reset controller, so it gets its own device tree node.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/boot/dts/tegra124.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git
Save and restore this register since the LP1 restore assembly routines
fiddle with it. Otherwise the CPU would keep running on PLLX after
resume from suspend even when DFLL was the original clocksource.
Signed-off-by: Tuomas Tynkkynen
---
drivers/clk/tegra/clk-tegra124.c | 14 ++
1
On 21 August 2014 02:19, Rusty Russell wrote:
> Arjun Sreedharan writes:
>> Do not leak memory when attrs is non NULL and
>> krealloc() fails. Without temporary variable,
>> reference to it is lost.
>>
>> Signed-off-by: Arjun Sreedharan
>
> ...
>
>> }
>> - /* Despite looking like the
On Thu, Aug 21, 2014 at 5:29 AM, Jim Davis wrote:
> The linux-next wiki at http://linux.f-seidel.de/linux-next/pmwiki has
> been gone for several months now.
Yes, I can't load the page, too. BTW, wouldn't it be better to add
Frank Seidel as recipient because he was the manager of the wiki?
I
The Tegra124 cpufreq driver relies on certain clocks being present
in the /cpus/cpu@0 node.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/boot/dts/tegra124.dtsi | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra124.dtsi
The cpufreq driver for Tegra124 will be a different one than the old
Tegra20 cpufreq driver (tegra-cpufreq), which does not use the device
tree.
Signed-off-by: Tuomas Tynkkynen
---
v3: vdd-cpu-supply property added
---
.../bindings/cpufreq/tegra124-cpufreq.txt | 44
The DFLL clocksource was missing from the list of possible parents for
the fast CPU cluster. Add it to the list.
Signed-off-by: Tuomas Tynkkynen
---
drivers/clk/tegra/clk-tegra-super-gen4.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
The Tegra124 cpufreq driver depends on CONFIG_GENERIC_CPUFREQ_CPU0, so
enable it to get the Tegra driver to build by default.
Signed-off-by: Tuomas Tynkkynen
---
v4: New patch
---
arch/arm/configs/tegra_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Add the CPU voltage regulator for the cpufreq driver.
Signed-off-by: Tuomas Tynkkynen
---
v3: New patch
---
arch/arm/boot/dts/tegra124-jetson-tk1.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/tegra124-jetson-tk1.dts
b/arch/arm/boot/dts/tegra124-jetson-tk1.dts
The Tegra124 will use a different driver for frequency scaling, so
rename the old driver (which handles only Tegra20) appropriately.
Signed-off-by: Tuomas Tynkkynen
---
v3: New patch
---
drivers/cpufreq/Kconfig.arm| 6 +++---
drivers/cpufreq/Makefile
Add a new cpufreq driver for Tegra124. Instead of using the PLLX as
the CPU clocksource, switch immediately to the DFLL. It allows the use
of higher clock rates, and will automatically scale the CPU voltage as
well. Besides the CPU clocksource switch, we let the cpufreq-cpu0 driver
for all the
Add basic platform driver support for the fast CPU cluster DFLL
clocksource found on Tegra124 SoCs. This small driver selects the
appropriate Tegra124-specific characterization data and integration
code. It relies on the DFLL common code to do most of the work.
Signed-off-by: Tuomas Tynkkynen
Add the board-specific properties of the DFLL for the Jetson TK1 board.
On this board, the DFLL will take control of the sd0 regulator on the
on-board AS3722 PMIC.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/boot/dts/tegra124-jetson-tk1.dts | 8 +++-
1 file changed, 7 insertions(+), 1
Add shared code to support the Tegra DFLL clocksource in open-loop
mode. This root clocksource is present on the Tegra124 SoCs. The
DFLL is the intended primary clock source for the fast CPU cluster.
This code is very closely based on a patch by Paul Walmsley from
December
The DFLL is the main clocksource for the fast CPU cluster on Tegra124
and also provides automatic CPU rail voltage scaling as well. The DFLL
is a separate IP block from the usual Tegra124 clock-and-reset
controller, so it gets its own node in the device tree.
Signed-off-by: Tuomas Tynkkynen
---
Yes, that looks good. While at it I grep'd the tree for
'CONFIG_JUMP_LABEL', and found some uses in the
netfilter code which should probably be
'HAVE_JUMP_LABEL' as well.
Thanks,
-Jason
On 08/20/2014 05:29 AM, Zhouyi Zhou wrote:
> jump_label_ratelimit.h is split from jump_label.h to enable the
sched_in preempt notifier is available for x86, allow its use in
specific virtualization technlogies as well.
Signed-off-by: Radim Krčmář
---
arch/x86/include/asm/kvm_host.h | 2 ++
arch/x86/kvm/svm.c | 6 ++
arch/x86/kvm/vmx.c | 6 ++
arch/x86/kvm/x86.c
ple_window is updated on every vmentry, so there is no reason to have it
read-only anymore.
ple_window* weren't writable to prevent runtime overflow races;
they are prevented by a seqlock.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/vmx.c | 48 +---
On platforms that do not power off during suspend, successfully entering
suspend races with timers.
The race happening in a couple of location is:
1. disable IRQs (e.g. arch_suspend_disable_irqs())
...
2. syscore_suspend()
-> timekeeping_suspend()
->
Change PLE window into per-VCPU variable, seeded from module parameter,
to allow greater flexibility.
Brings in a small overhead on every vmentry.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/vmx.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx.c
Introduce preempt notifiers for architecture specific code.
Advantage over creating a new notifier in every arch is slightly simpler
code and guaranteed call order with respect to kvm_sched_in.
Signed-off-by: Radim Krčmář
---
arch/arm/kvm/arm.c | 4
arch/mips/kvm/mips.c | 4
Window is increased on every PLE exit and decreased on every sched_in.
The idea is that we don't want to PLE exit if there is no preemption
going on.
We do this with sched_in() because it does not hold rq lock.
There are two new kernel parameters for changing the window:
ple_window_grow and
Tracepoint for dynamic PLE window, fired on every potential change.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/trace.h | 25 +
arch/x86/kvm/vmx.c | 8 +---
arch/x86/kvm/x86.c | 1 +
3 files changed, 31 insertions(+), 3 deletions(-)
diff --git
v1 -> v2:
* squashed [v1 4/9] and [v1 5/9] (clamping)
* dropped [v1 7/9] (CPP abstractions)
* merged core of [v1 9/9] into [v1 4/9] (automatic maximum)
* reworked kernel_param_ops: closer to pure int [v2 6/6]
* introduced ple_window_actual_max & reworked clamping [v2 4/6]
* added seqlock for
On 08/20/2014 01:39 PM, David Woodhouse wrote:
> On Wed, 2014-08-20 at 12:21 -0700, Tadeusz Struk wrote:
>> Hi David,
>> On 08/20/2014 11:34 AM, David Woodhouse wrote:
>>> I'm not sure I understand. Precisely what fails?
>>
>> I clone a subsystem, configure it to use
>>
Arjun Sreedharan writes:
> Do not leak memory when attrs is non NULL and
> krealloc() fails. Without temporary variable,
> reference to it is lost.
>
> Signed-off-by: Arjun Sreedharan
...
> }
> - /* Despite looking like the typical realloc() bug, this is safe.
> - * We *want*
Write back!!!
I, Liliane authenticate this email, you can read about me on:
http://en.wikipedia.org/wiki/Liliane_Bettencourt
I write to you because I intend to give to you a portion of my
Net-worth which I have been banking. I want to cede it out as gift
hoping it would be of help to you and
Heiko,
On Wed, Aug 20, 2014 at 11:03 AM, Heiko Stübner wrote:
> Am Mittwoch, 20. August 2014, 09:27:02 schrieb Doug Anderson:
>> Heiko,
>>
>> On Wed, Aug 20, 2014 at 9:20 AM, Heiko Stübner wrote:
>> > Am Mittwoch, 20. August 2014, 08:55:09 schrieb Doug Anderson:
>> >> Thierry,
>> >>
>> >> On
Signed-off-by: Soren Brinkmann
---
.../devicetree/bindings/memory-controllers/synopsys.txt | 11 +++
1 file changed, 11 insertions(+)
create mode 100644
Documentation/devicetree/bindings/memory-controllers/synopsys.txt
diff --git
The DDR controller can detect idle periods and leverage low power
features like self-refresh and clock stop.
When new requests occur, the DDRC resumes normal operation.
Signed-off-by: Soren Brinkmann
---
arch/arm/mach-zynq/Makefile | 2 +-
arch/arm/mach-zynq/common.c | 1 +
From: Daniel Lezcano
The core is not powered down, it is pointless to call the cpu_pm notifiers and
switch to the global timer.
Signed-off-by: Daniel Lezcano
Reviewed-and-tested-by: Soren Brinkmann
---
drivers/cpuidle/cpuidle-zynq.c | 10 +-
1 file changed, 1 insertion(+), 9
From: Daniel Lezcano
As there is no Power management unit on this board, it is not possible to power
down a core, just WFI is allowed. There is no point to invalidate the cache and
exit coherency.
Signed-off-by: Daniel Lezcano
Reviewed-and-tested-by: Soren Brinkmann
---
Avoid races and add synchronisation between the arch specific
kill and die routines.
The same synchronisation issue was fixed on IMX platform
by this commit:
"ARM: imx: fix sync issue between imx_cpu_die and imx_cpu_kill"
(sha1: 2f3edfd7e27ad4206acbc2ae99c9df5f46353024)
Signed-off-by: Soren
Match the naming pattern of all other SMP ops and rename
zynq_platform_cpu_die --> zynq_cpu_die.
Signed-off-by: Soren Brinkmann
---
arch/arm/mach-zynq/platsmp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-zynq/platsmp.c b/arch/arm/mach-zynq/platsmp.c
On Wed, 20 Aug 2014, Stephen Boyd wrote:
> Commit 1a6b69b6548c (ARM: gic: add CPU migration support,
> 2012-04-12) introduced an acquisition of the irq_controller_lock
> in gic_raise_softirq() which can lead to a spinlock recursion if
> the gic_arch_extn hooks call into the scheduler (via
The hotplug code contains only a single function, which is an SMP
function. Move that to platsmp.c where all other SMP runctions reside.
That allows removing hotplug.c and declaring the cpu_die function
static.
Signed-off-by: Soren Brinkmann
---
arch/arm/mach-zynq/Makefile | 1 -
Signed-off-by: Soren Brinkmann
---
arch/arm/mach-zynq/common.c | 6 ++
arch/arm/mach-zynq/common.h | 11 +++
arch/arm/mach-zynq/platsmp.c | 9 +
3 files changed, 26 insertions(+)
diff --git a/arch/arm/mach-zynq/common.c b/arch/arm/mach-zynq/common.c
index
101 - 200 of 1818 matches
Mail list logo
