Every cache that is considered a root cache (basically the "original" caches,
tied to the root memcg/no-memcg) will have an array that should be large enough
to store a cache pointer per each memcg in the system.
Theoreticaly, this is as high as 1 << sizeof(css_id), which is currently in the
64k
SLAB allows us to tune a particular cache behavior with tunables.
When creating a new memcg cache copy, we'd like to preserve any tunables
the parent cache already had.
This could be done by an explicit call to do_tune_cpucache() after the
cache is created. But this is not very convenient now
On Thu, 2012-10-18 at 11:32 +0400, Vladimir Davydov wrote:
>
> 1) Do you agree that the problem exists and should be sorted out?
This is two questions.. yes it exists, I'm absolutely sure I pointed it
out as soon as people even started talking about this nonsense (bw
cruft).
Should it be
Hello Andrew and Oleg,
Andrew, what do you think about this patch? I reworked it according
with your comments to the previous version.
Oleg, could you send Ack in this version, if it's ok for you.
Thanks.
2012/10/12 Andrew Vagin :
> 'struct pid' is a "variable sized struct" - a header with an
This patch moves all the common machinery to slabinfo processing
to slab_common.c. We can do better by noticing that the output is
heavily common, and having the allocators to just provide finished
information about this. But after this first step, this can be done
easier.
Signed-off-by: Glauber
We are able to match a cache allocation to a particular memcg. If the
task doesn't change groups during the allocation itself - a rare event,
this will give us a good picture about who is the first group to touch a
cache page.
This patch uses the now available infrastructure by calling
This patch implements destruction of memcg caches. Right now,
only caches where our reference counter is the last remaining are
deleted. If there are any other reference counters around, we just
leave the caches lying around until they go away.
When that happen, a destruction function is called
The header format is highly similar between slab and slub. The main
difference lays in the fact that slab may optionally have statistics
added here in case of CONFIG_SLAB_DEBUG, while the slub will stick them
somewhere else.
By making sure that information conditionally lives inside a
In the slub allocator, when the last object of a page goes away, we
don't necessarily free it - there is not necessarily a test for empty
page in any slab_free path.
This means that when we destroy a memcg cache that happened to be empty,
those caches may take a lot of time to go away: removing
This enables us to remove all the children of a kmem_cache being
destroyed, if for example the kernel module it's being used in
gets unloaded. Otherwise, the children will still point to the
destroyed parent.
Signed-off-by: Suleiman Souhlal
Signed-off-by: Glauber Costa
CC: Christoph Lameter
Signed-off-by: Glauber Costa
CC: Christoph Lameter
CC: Pekka Enberg
CC: Michal Hocko
CC: Kamezawa Hiroyuki
CC: Johannes Weiner
CC: Suleiman Souhlal
CC: Tejun Heo
---
Documentation/cgroups/memory.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
After the slab/slub/slob merge, we are deleting the element from the
slab_cache lists, and then if the destruction fail, we add it back
again. This behavior was present in some caches, but not in others, if
my memory doesn't fail me.
I, however, see no reason why we need to do so, since we are
Allow a memcg parameter to be passed during cache creation. When the slub
allocator is being used, it will only merge caches that belong to the same
memcg.
Default function is created as a wrapper, passing NULL to the memcg version. We
only merge caches that belong to the same memcg.
A helper
With all the infrastructure in place, we can now have slabinfo_show
done from slab_common.c. A cache-specific function is called to grab
information about the cache itself, since that is still heavily
dependent on the implementation. But with the values produced by it, all
the printing and
When we create caches in memcgs, we need to display their usage
information somewhere. We'll adopt a scheme similar to /proc/meminfo,
with aggregate totals shown in the global file, and per-group
information stored in the group itself.
For the time being, only reads are allowed in the per-group
This patch creates a mechanism that skip memcg allocations during
certain pieces of our core code. It basically works in the same way
as preempt_disable()/preempt_enable(): By marking a region under
which all allocations will be accounted to the root memcg.
We need this to prevent races in early
For the kmem slab controller, we need to record some extra
information in the kmem_cache structure.
Signed-off-by: Glauber Costa
Signed-off-by: Suleiman Souhlal
CC: Christoph Lameter
CC: Pekka Enberg
CC: Michal Hocko
CC: Kamezawa Hiroyuki
CC: Johannes Weiner
CC: Tejun Heo
---
struct page already have this information. If we start chaining
caches, this information will always be more trustworthy than
whatever is passed into the function
A parent pointer is added to the slub structure, so we can make sure
the freeing comes from either the right slab, or from its
Note: This is basically the same as v4. During this week, I made some changes
to this series in advance based on the feedback I had in the kmemcg-stack
last submission. Although the last series was not yet extensively reviewed,
I opted for sending this out so you guys have the most up2date code to
On Fri, Oct 19, 2012 at 3:45 PM, Sjur Brændeland wrote:
> Has anyone started looking into any of the open issues mentioned above?
No - feel free to take a stab at it.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
At 2012/10/19 18:44, Wen Congyang Wrote:
At 10/06/2012 03:27 AM, KOSAKI Motohiro Wrote:
On Thu, Oct 4, 2012 at 10:25 PM, Yasuaki Ishimatsu
wrote:
When calling remove_memory(), the memory should be offline. If the function
is used to online memory, kernel panic may occur.
So the patch checks
On Fri, 19 Oct 2012, Ezequiel Garcia wrote:
> Fields object_size and size are not the same: the latter might include
> slab metadata. Return object_size field in kmem_cache_size().
> Also, improve trace accuracy by correctly tracing reported size.
Acked-by: Christoph Lameter
--
To unsubscribe
On Fri, 19 Oct 2012, Ezequiel Garcia wrote:
> This function is identically defined in all three allocators
> and it's trivial to move it to slab.h
>
> Since now it's static, inline, header-defined function
> this patch also drops the EXPORT_SYMBOL tag.
Acked-by: Christoph Lameter
--
To
On Wed, 2012-10-17 at 11:35 -0400, Vince Weaver wrote:
>
> This is by accident; it looks like the code does
>val |= ARCH_PERFMON_EVENTSEL_ENABLE;
> in p6_pmu_disable_event() so that events are never truly disabled
> (is this a bug? should it be &=~ instead?).
I think that's on purpose..
On Fri, Oct 19, 2012 at 01:45:27PM +0800, Tang Chen wrote:
> cmci_rediscover() is only called by the CPU_POST_DEAD event handler,
> which means the corresponding cpu has already dead. As a result, it
> won't be accessed in the for_each_online_cpu loop.
> So, we could change the if(cpu == dying)
On 10/19/2012 07:41 AM, Peter Zijlstra wrote:
On Thu, 2012-10-18 at 17:20 -0400, Rik van Riel wrote:
Having the function name indicate what the function is used
for makes the code a little easier to read. Furthermore,
the fault handling code largely consists of do__page
functions.
I
Adding Arnd and Olof.
On 10/18/2012 07:04 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Let ARCH_MXC be covered by multi_v7_defconfig.
>
> Allow booting mx6 via NFS.
Now we can start debating what should or shouldn't be in shared
defconfigs. :)
My intent with this defconfig was to only
I made a correction on a line which has > 80 characters
also, aligned the consecutive line to meet the --strict rule.
Signed-off-by: Sangho Yi
---
drivers/mmc/core/bus.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/core/bus.c b/drivers/mmc/core/bus.c
On Fri, Oct 19, 2012 at 04:25:47PM +0530, Srivatsa S. Bhat wrote:
> Move the check for populated_zone() to the control statement of the
> 'for' loop and get rid of the odd looking if/else block.
>
> Signed-off-by: Srivatsa S. Bhat
> ---
>
> include/linux/mmzone.h |7 ++-
> 1 file
On Thu, Oct 18, 2012 at 10:05:39AM -0700, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 713f937655c4b15131b5a0eae4610918a4febe17
> Gitweb: http://git.kernel.org/tip/713f937655c4b15131b5a0eae4610918a4febe17
> Author: Peter Zijlstra
> AuthorDate: Fri, 12 Oct 2012 19:30:14 +0200
>
On Fri, Oct 19, 2012 at 02:40:58PM +0200, Benoit Cousson wrote:
> Hi Matt,
>
> On 10/19/2012 01:30 PM, Matt Porter wrote:
> > On Fri, Oct 19, 2012 at 10:24:15AM +0200, Benoit Cousson wrote:
> >> Hi Avinash,
> >>
> >> This look good to me except the: status = "disabled".
> >>
> >> The "disabled"
This is an updated version of the patch. I have dropped
.__DEPRECATED_clear_css_refs in this one as it makes the best sense to
me. I didn't add Tejun's Reviewed-by because of this change. Could you
recheck, please?
---
>From 6c1f2e76e254e7638ad8cc87f319e3492ac80c5b Mon Sep 17 00:00:00 2001
From:
Hi,
On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen wrote:
> The general direction I have in mind is to put the resource table in
> its final location while we do the first pass of fw parsing.
>
> This will solve all sort of open issues we have (or going to have soon):
>
> 1.
On 19 October 2012 15:45, Shiraz Hashim wrote:
> diff --git a/Documentation/devicetree/bindings/pwm/spear-pwm.txt
> b/Documentation/devicetree/bindings/pwm/spear-pwm.txt
> +pwm: pwm@a800 {
> +compatible ="st,spear320-pwm";
> +reg = <0xa800 0x1000>;
> +
On 10/18/2012 03:20 PM, Andrew Morton wrote:
> On Wed, 17 Oct 2012 08:09:55 -0700
> Dave Hansen wrote:
>>> +#ifdef CONFIG_MEMORY_FAILURE
>>> +static void clear_hwpoisoned_pages(struct page *memmap, int nr_pages)
>>> +{
>>> + int i;
>>> +
>>> + if (!memmap)
>>> + return;
>>
>> I
Always try and CC people who wrote the code..
On Fri, 2012-10-19 at 16:36 +0800, Xiaotian Feng wrote:
> There's a regression from commit 800d4d30, in autogroup_move_group()
>
> p->signal->autogroup = autogroup_kref_get(ag);
>
> if (!ACCESS_ONCE(sysctl_sched_autogroup_enabled))
>
On Friday 19 October 2012 11:36:25 Fainelli wrote:
> Sebastian Andrzej Siewior linutronix.de> writes:
> >
> > No. You do have a compatible entry. It first appeared on the ce4100
> > CPU. If it happens to also work on the n450 then it seems to be
> > compatible with that one. "This" is
Il 19/10/2012 15:29, Paul Holland ha scritto:
> A disadvantage of solutions in this direction, which was not preset in
> Paton's patch, is that all calls to epoll_wait would need to specify some
> timeout value (!= -1) to guarantee that they each come out of epoll_wait
> and execute the "pass the
On 10/19/12 6:03 AM, "Paolo Bonzini" wrote:
>Il 18/10/2012 20:05, Andy Lutomirski ha scritto:
>>
>> Unless something is rather buggy in kernel land (and I don't think it
>> is), once EPOLL_CTL_DEL has returned, no call to epoll_wait that starts
>> *after* EPOLL_CTL_DEL finishes will return that
Hi guys,
below is a RAS fix which reverts the addition of a sysfs attribute
which we agreed is not needed, post-factum. And this should go in now
because that sysfs attribute is going to end up in 3.7 otherwise and
thus exposed to userspace; removing it then would be a lot harder.
Thanks.
The
Ingo Molnar wrote:
> What we want in .c files are not ../.. inclusions but the
> 'seemless' inclusions. Which is the overwhelming
> majority, gladly. Do we want to make that the 100% majority?
I think this is going to be necessary for when x86 gets merged. x86's
asm/unistd.h #includes
On Thu 18-10-12 15:46:06, Tejun Heo wrote:
> On Thu, Oct 18, 2012 at 03:41:48PM -0700, Tejun Heo wrote:
> > Note that the patch is broken in a couple places but it does show the
> > general direction. I'd prefer if patch #3 simply makes pre_destroy()
> > return 0 and drop
On Thu 18-10-12 15:41:48, Tejun Heo wrote:
> Hello, Michal.
>
> On Wed, Oct 17, 2012 at 03:30:46PM +0200, Michal Hocko wrote:
> > Now that mem_cgroup_pre_destroy callback doesn't fail finally we can
> > safely move on and forbit all the callbacks to fail. The last missing
> > piece is moving
On Thu, Oct 18, 2012 at 12:44:16PM +0100, Stefano Stabellini wrote:
> On Thu, 18 Oct 2012, Mukesh Rathor wrote:
> > PVH: balloon and grant changes. For balloon changes we skip setting of
> > local p2m as it's updated in xen. For grant, the shared grant frame is the
> > pfn and not mfn, hence its
On Fri, 2012-10-19 at 14:00 +0530, Raghavendra K T wrote:
> On 10/15/2012 08:04 PM, Andrew Theurer wrote:
> > On Mon, 2012-10-15 at 17:40 +0530, Raghavendra K T wrote:
> >> On 10/11/2012 01:06 AM, Andrew Theurer wrote:
> >>> On Wed, 2012-10-10 at 23:24 +0530, Raghavendra K T wrote:
> On
From: Ulf Hansson
The below commit introduced a compile error for a missing include file.
ASoC: ux500_msp_i2s: better use devm functions and fix error return code
Signed-off-by: Ulf Hansson
---
sound/soc/ux500/ux500_msp_i2s.c |1 +
1 file changed, 1 insertion(+)
diff --git
From: Ulf Hansson
Likely during merge of the below commits ended up breaking compilation:
ASoC: Ux500: Enable ux500 MSP driver for Device Tree
ASoC: ux500_msp_i2s: better use devm functions and fix error return code
Signed-off-by: Ulf Hansson
---
sound/soc/ux500/ux500_msp_i2s.c | 18
> > +config XEN_X86_PVH
> > + bool "Support for running as a PVH guest (EXPERIMENTAL)"
> > + depends on X86_64 && XEN && EXPERIMENTAL
> > + default n
> > + help
> > + This option enables support for running as a PVH guest (PV guest
> > + using hardware extensions) under a
> On Fri, Oct 19, 2012 at 04:43:09PM +0800, Guan Xuetao wrote:
>> From: Al Viro
>>
>> Signed-off-by: Al Viro
>> Acked-and-Tested-by: Guan Xuetao
>
> You mean, it worked modulo obvious missing ')'? Wow... OK, merged
> into signal.git#for-next, obviously in no-rebase mode (as the matter
> of
On Thu 18-10-12 15:16:54, Tejun Heo wrote:
> Hello, Michal.
>
> On Wed, Oct 17, 2012 at 03:30:45PM +0200, Michal Hocko wrote:
> > mem_cgroup_force_empty_list currently tries to remove all pages from
> > the given LRU. To prevent from temoporary failures (EBUSY returned by
> >
On Wed, Oct 17, 2012 at 05:26:42PM -0700, Mukesh Rathor wrote:
> [PATCH 1/6] PVH: is a PV linux guest that has extended capabilities. This
> patch allows it to be configured and enabled. Also, basic header file changes
> to add new subcalls to physmap hypercall. Lastly, mfn_to_local_pfn must
>
On Fri, Oct 19, 2012 at 04:43:09PM +0800, Guan Xuetao wrote:
> From: Al Viro
>
> Signed-off-by: Al Viro
> Acked-and-Tested-by: Guan Xuetao
You mean, it worked modulo obvious missing ')'? Wow... OK, merged
into signal.git#for-next, obviously in no-rebase mode (as the matter
of fact, I'm
On Thu, Oct 18, 2012 at 11:03:38AM +0100, David Vrabel wrote:
> From: David Vrabel
>
> Backend drivers shouldn't transistion to CLOSED unless the frontend is
> CLOSED. If a backend does transition to CLOSED too soon then the
> frontend may not see the CLOSING state and will not properly
On Thu, Oct 18, 2012 at 11:03:37AM +0100, David Vrabel wrote:
> From: David Vrabel
>
> Backend drivers shouldn't transistion to CLOSED unless the frontend is
> CLOSED. If a backend does transition to CLOSED too soon then the
> frontend may not see the CLOSING state and will not properly
On Thu, Oct 18, 2012 at 11:03:36AM +0100, David Vrabel wrote:
> From: David Vrabel
>
> Backend drivers shouldn't transistion to CLOSED unless the frontend is
> CLOSED. If a backend does transition to CLOSED too soon then the
> frontend may not see the CLOSING state and will not properly
Currently the __define_initcall macro takes three arguments, fn, id
and level. The level argument is exactly the same as the id argument
but wrapped in quotes. To overcome this need to specify three
arguments to the __define_initcall macro, where one argument is the
stringification of another, we
From: Linus Walleij
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
However this does not work for us, because we want to use the
same set of pins
Virtio devices may attempt to add descriptors to a virtqueue from atomic
context using GFP_ATOMIC allocation. This is problematic because such
allocations can fall outside of the lowmem mapping, causing virt_to_phys
to report bogus physical addresses which are subsequently passed to
userspace via
Some virtio device drivers (9p) need to translate high virtual addresses
to physical addresses, which are inserted into the virtqueue for
processing by userspace.
This patch exports the kmap_to_page symbol, so that the affected drivers
can be compiled as modules.
Signed-off-by: Will Deacon
---
When using a virtio transport, the 9p net device may pass the physical
address of a kernel buffer to userspace via a scatterlist inside a
virtqueue. If the kernel buffer is mapped outside of the linear mapping
(e.g. highmem), then virt_to_page will return a bogus value and we will
populate the
Il 18/10/2012 20:05, Andy Lutomirski ha scritto:
>
> Unless something is rather buggy in kernel land (and I don't think it
> is), once EPOLL_CTL_DEL has returned, no call to epoll_wait that starts
> *after* EPOLL_CTL_DEL finishes will return that object. This suggests
> an RCU-like approach:
Please pull nfsd bugfixes for 3.7 from the for-3.7 branch at:
git://linux-nfs.org/~bfields/linux.git for-3.7
--b.
Sasha Levin (1):
SUNRPC: Prevent kernel stack corruption on long values of flush
Trond Myklebust (1):
On 10/19/2012 02:06 AM, AnilKumar Ch wrote:
> Add device tree support to matrix keypad driver and usage details
> are added to device tree documentation. Driver was tested on AM335x
> EVM.
>
> Signed-off-by: AnilKumar Ch
> ---
> .../devicetree/bindings/input/matrix-keypad.txt| 52
On Thu, Oct 18, 2012 at 06:48:16AM +0100, Geert Uytterhoeven wrote:
> On Thu, Oct 18, 2012 at 2:04 AM, Benjamin Herrenschmidt
> wrote:
> > The sort story is that endianness is not a property of the IO port but
> > of the information that transit through it. If you're just going to copy
> > it
On Fri, Oct 19, 2012 at 1:33 AM, Stephen Warren wrote:
> On 10/18/2012 04:01 AM, Linus Walleij wrote:
>> This switches the way that pins are reserved for multiplexing:
>
> The conceptual change makes perfect sense to me.
Thanks...
>> diff --git a/drivers/pinctrl/pinmux.c
On Fri, 2012-10-19 at 01:21 -0400, Dave Jones wrote:
> > Not sure why you are CC'ing a call site, rather than the maintainers of
> > the code. Just looks like lockdep is using too small a static value.
> > Though it is pretty darn large...
>
> You're right, it's a huge chunk of memory.
> It
On 10/19/2012 02:12 AM, Kim, Milo wrote:
> To get the battery voltage and temperature, IIO ADC functions are used.
> LP8788 ADC driver provides RAW and SCALE channel information.
> This patch fixes wrong ADC result.
>
> Patch v2.
> Use simple iio_read_channel_processed() function rather than
Hi Matt,
On 10/19/2012 01:30 PM, Matt Porter wrote:
> On Fri, Oct 19, 2012 at 10:24:15AM +0200, Benoit Cousson wrote:
>> Hi Avinash,
>>
>> This look good to me except the: status = "disabled".
>>
>> The "disabled" should be reserved for variant that does not contain the IP.
>> Is it the case
On Thu, 2012-10-18 at 15:28 -0400, Mikulas Patocka wrote:
>
> On Thu, 18 Oct 2012, Oleg Nesterov wrote:
>
> > Ooooh. And I just noticed include/linux/percpu-rwsem.h which does
> > something similar. Certainly it was not in my tree when I started
> > this patch... percpu_down_write() doesn't
This function is identically defined in all three allocators
and it's trivial to move it to slab.h
Since now it's static, inline, header-defined function
this patch also drops the EXPORT_SYMBOL tag.
Cc: Christoph Lameter
Cc: Pekka Enberg
Cc: Matt Mackall
Signed-off-by: Ezequiel Garcia
---
Fields object_size and size are not the same: the latter might include
slab metadata. Return object_size field in kmem_cache_size().
Also, improve trace accuracy by correctly tracing reported size.
Cc: Christoph Lameter
Cc: Pekka Enberg
Cc: Matt Mackall
Acked-by: David Rientjes
Signed-off-by:
This field was being used to store size allocation so it could be
retrieved by ksize(). However, it is a bad practice to not mark a page
as a slab page and then use fields for special purposes.
There is no need to store the allocated size and
ksize() can simply return PAGE_SIZE <<
On Thu, Oct 18, 2012 at 7:46 PM, David Rientjes wrote:
> On Thu, 18 Oct 2012, Ezequiel Garcia wrote:
>
>> This field was being used to store size allocation so it could be
>> retrieved by ksize(). However, it is a bad practice to not mark a page
>> as a slab page and then use fields for special
From: Matt Fleming
Calling __pa() with an ioremap'd address is invalid. If we
encounter an efi_memory_desc_t without EFI_MEMORY_WB set in
->attribute we currently call set_memory_uc(), which in turn
calls __pa() on a potentially ioremap'd address. On
CONFIG_X86_32 this results in the following
Hi Mauro,
(CC'ing LKML)
On Friday 19 October 2012 08:21:16 Mauro Carvalho Chehab wrote:
> Em Fri, 19 Oct 2012 07:43:11 -0300
>
> Mauro Carvalho Chehab escreveu:
> > -#include
> > -#include
> > -
> > -#endif /*_DVBDMX_H_*/
>
> Just to not discard a valid comment on IRC, Laurent proposed that
Hi Paul,
I think that you have forgot to reset .usage_avg_sum in the
__sched_fork as it's already done for .runnable_avg_sum and
.usage_avg_sum
And it seems that this reset is not corrected in the latest version in
your git repo:
On 10/19/2012 01:41 AM, Marcos Paulo de Souza wrote:
> This commit simplifies the exit of probe function, by returning
> directly when it don't need to release any resources.
>
> Signed-off-by: Marcos Paulo de Souza
Looks good, but I'd just fold the relevant parts in the previous patches.
>
Yann E. MORIN wrote:
> Some systems (eg. Cygwin, FreeBSD) are missing the CIRCLEQ macros.
> They were removed in Y2000 from FreeBSD:
> http://svnweb.freebsd.org/base?view=revision=70469
>
> The reason was that TAILQ are perfectly capable of doing the exact
> same things:
>
>
On Fri, Oct 19, 2012 at 16:45:58, Porter, Matt wrote:
> On Fri, Oct 19, 2012 at 10:26:20AM +, Bedia, Vaibhav wrote:
[...]
> >
> > I didn't see all the patches that you posted on edma-dmaengine-v3
> > but I do seem them on edma-dmaengine-am33xx-v3 branch.
>
> I see I referenced the wrong
Commit-ID: c1a305006e4dd428001852923c11806d754db9f1
Gitweb: http://git.kernel.org/tip/c1a305006e4dd428001852923c11806d754db9f1
Author: Rik van Riel
AuthorDate: Thu, 18 Oct 2012 17:19:28 -0400
Committer: Ingo Molnar
CommitDate: Fri, 19 Oct 2012 13:45:48 +0200
numa: Add credits for NUMA
From: Maxime Bizon
record_size / console_size / ftrace_size can be 0 (this is how you
disable the feature), but rounddown_pow_of_two(0) is undefined. This problem
has been present since commit 1894a253 (ramoops: Move to fs/pstore/ram.c).
Signed-off-by: Maxime Bizon
Signed-off-by: Florian
Hi,
on the new opteron server i'm observing an oops during matrox video
initialization.
here's the dmesg from pure 3.6.2 kernel:
[ 20.598985] [drm] Initialized drm 1.1.0 20060810
[ 20.642302] [drm:mga_vram_init] *ERROR* can't reserve VRAM
[ 20.642307] mgag200 :01:04.0: Fatal error
From: Maxime Bizon
Some CE4100 devices such as the:
- DFX module (01:0b.7)
- entertainment encryption device (01:10.0)
- multimedia controller (01:12.0)
do not have a device interrupt at all. This patch fixes the PCI controller
code to declare the missing PCI configuration register space, as
From: Maxime Bizon
The default reboot is via ACPI for this platform, and the CEFDK bootloader
actually supports this, but will issue a system power off instead of a real
reboot. Setting the reboot method to be KBD instead of ACPI ensures proper
system reboot.
Signed-off-by: Florian Fainelli
The CE4100 platform is currently missing a proper pm_poweroff implementation
leading to poweroff making the CPU spin forever and the CE4100 platform does
not enter a low-power mode where the external Power Management Unit can
properly power off the system. Power off on this platform is implemented
Hi all,
This patch serie contains shutdown/reboot fixes for the CE4100 platform as
well as a PCI controller fix for devices without an interrupt line.
Florian Fainelli (3):
x86: ce4100: implement pm_poweroff
x86: ce4100: force reboot method to be KBD
x86: ce4100: fixup PCI configuration
On 10/19/2012 12:35 PM, Linus Walleij wrote:
> On Thu, Oct 18, 2012 at 12:07 PM, Roland Stigge wrote:
>> On 10/17/2012 09:05 PM, Greg KH wrote:
+if (value != exported) {
+if (value)
+status = gpio_block_value_export(block);
+
On Thu, Oct 18, 2012 at 9:16 PM, Rusty Russell wrote:
> Josh Boyer writes:
>> On Thu, Oct 18, 2012 at 2:46 PM, Linus Torvalds
>> wrote:
>>> On Wed, Oct 17, 2012 at 10:34 PM, Rusty Russell
>>> wrote:
Hacking the keyid and signer-name to be extracted every time by
sign-file takes
Sebastian Andrzej Siewior linutronix.de> writes:
>
> No. You do have a compatible entry. It first appeared on the ce4100
> CPU. If it happens to also work on the n450 then it seems to be
> compatible with that one. "This" is documented somewhere…
> Usually you add 'compatible = "your cpu",
On Thu, Oct 18, 2012 at 8:48 PM, Rusty Russell wrote:
> Josh Boyer writes:
>> It might even be able to be moved entirely into scripts/Makefile.modinst
>> but I haven't gotten that far yet.
>
> Thanks, I'll add this.
Excellent.
> Note it was word-wrapped here though :(
Sigh. Sorry, Rusty. I
On Thu, 2012-10-18 at 17:19 -0400, Rik van Riel wrote:
> The NUMA placement code has been rewritten several times, but
> the basic ideas took a lot of work to develop. The people who
> put in the work deserve credit for it. Thanks Andrea & Peter :)
>
> The Documentation/scheduler/numa-problem.txt
On Thu, 2012-10-18 at 17:20 -0400, Rik van Riel wrote:
> Having the function name indicate what the function is used
> for makes the code a little easier to read. Furthermore,
> the fault handling code largely consists of do__page
> functions.
I don't much care either way, but I was
Am 19.10.2012 13:25, schrieb David Howells:
Stephen Rothwell wrote:
So, this still generates the keys during the normal build, right? That
would be a problem for build servers that have limited randomness
available to them, I think.
openssl uses /dev/urandom (unlike gpg), so that's less of
H. Peter Anvin zytor.com> writes:
> > It is a bit more indirect, but also in practice it's a bit trickier than
> > that. We need to ensure the memory doesn't change underneath us and
> > stays attached to that fd. I can easily see that code slipping and
> > ending in an exploit.
> >
> > But
Hi David,
On Fri, 19 Oct 2012 12:25:23 +0100 David Howells wrote:
>
> Stephen Rothwell wrote:
>
> > So, this still generates the keys during the normal build, right? That
> > would be a problem for build servers that have limited randomness
> > available to them, I think.
>
> openssl uses
On Fri, Oct 19, 2012 at 10:24:15AM +0200, Benoit Cousson wrote:
> Hi Avinash,
>
> This look good to me except the: status = "disabled".
>
> The "disabled" should be reserved for variant that does not contain the IP.
> Is it the case here?
Microsoft Digital Media Keyboard 3000 has two interfaces, and the
second one has a report descriptor with a bug. The second collection
says:
05 01 -- global; usage page -- 01 -- Generic Desktop Controls
09 80 -- local; usage -- 80 -- System Control
a1 01 -- main; collection -- 01 -- application
Stephen Rothwell wrote:
> So, this still generates the keys during the normal build, right? That
> would be a problem for build servers that have limited randomness
> available to them, I think.
openssl uses /dev/urandom (unlike gpg), so that's less of a problem.
David
--
To unsubscribe from
Rusty Russell wrote:
> > (Side note: I hope people realize that the random key is generated
> > with a 100-year lifespan. So if you build a kernel today, you do
> > potentially have a "year-2112 problem". I'm not horribly worried, but
> > I *am* a bit worried about 32-bit time_t overflow and I
On Wed, 2012-10-17 at 20:29 -0700, David Rientjes wrote:
>
> Ok, thanks for the update. I agree that we should be clearing the mapping
> at node hot-remove since any cpu that would subsequently get onlined and
> assume one of the previous cpu's ids is not guaranteed to have the same
>
301 - 400 of 1116 matches
Mail list logo
