On Thu, Mar 14, 2013 at 02:52:35PM +, Dimitris Papastamos wrote:
> if (rbnode) {
> reg_tmp = (reg - rbnode->base_reg) / map->reg_stride;
> + /* Does this register exist? If not bail out. */
> + if (!(rbtree_ctx->reg_present[BIT_WORD(reg)] & BIT_MASK
于 2013年03月14日 22:05, Greg KH 写道:
On Thu, Mar 14, 2013 at 09:51:34PM +0800, Shuge wrote:
Hi all,
When the kernel printk too many log, the cpu is failed to come online.
The problem is this:
For example, cpu0 bring up cpu1:
a. cpu0 call cpu_up:
cpu_up()
->_cpu_up()
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> + page_cache_get(page);
> + spin_lock_irq(&mapping->tree_lock);
> + page->mapping = mapping;
> + page->index = offset;
> + error = radix_tree_insert(&mapping->page_tree, offset, page);
> + if (unlikely
On Friday, March 15, 2013 8:01 AM, Doug Anderson wrote:
>
> The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
> using the common clock framework. Document it.
>
> Signed-off-by: Doug Anderson
> ---
> Documentation/devicetree/bindings/usb/exynos-usb.txt | 10 ++
> 1 f
在 2013-03-15五的 09:01 +0800，Li Zefan写道：
> On 2013/3/15 8:20, li guang wrote:
> > 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
> >> On 03/14, liguang wrote:
> >>>
> >>> Signed-off-by: liguang
> >>> ---
> >>> kernel/task_work.c |3 ++-
> >>> 1 files changed, 2 insertions(+), 1 deletions(-)
> >>>
This driver supports host initiated backup of the guest. On Windows guests,
the host can generate application consistent backups using the Windows VSS
framework. On Linux, we ensure that the backup will be file system consistent.
This driver allows the host to initiate a "Freeze" operation on all
On Thu, Mar 14, 2013 at 02:43:32PM +0100, Miklos Szeredi wrote:
> > Either way, I suggest the next step is to ask Stephen to line this up
> > in linux-next.
>
> Al, are you okay with that? Or do you want it to go though -vfs?
Umm... I would prefer it to go through vfs.git, with serious modific
On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
> On 03/14/2013 03:28 AM, Bill Huang wrote:
> > On Thu, 2013-03-14 at 17:21 +0800, Peter De Schrijver wrote:
> >> On Thu, Mar 14, 2013 at 03:15:11AM +0100, Bill Huang wrote:
> >>
> >>> I don't think deferring will work either, considering the
On Thu, Mar 14, 2013 at 5:24 PM, Stephane Eranian wrote:
>
> I bet if you force the affinity of your perf record to be on
> a CPU other than CPU0, you will not get the crash.
>
> This is what I am seeing now. I appears on resume,
> CPU0 hotplug callbacks for perf_events are not invoked
> leaving D
On 2013/3/15 8:20, li guang wrote:
> 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
>> On 03/14, liguang wrote:
>>>
>>> Signed-off-by: liguang
>>> ---
>>> kernel/task_work.c |3 ++-
>>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/kernel/task_work.c b/kernel/task_work.c
Hi Artem,
Today's linux-next merge of the l2-mtd tree got a conflict in
include/linux/mtd/nand.h between commit 5bc7c33ca93a ("mtd: nand:
reintroduce NAND_NO_READRDY as NAND_NEED_READRDY") from the mtd tree and
commit edac3311879c ("mtd: nand: remove AG-AND support") from the l2-mtd
tree.
I fixed
From: Yanchuan Nian
Since read can use stateid's from opens that only requested write access,
the value returned from access_permit_read() will always be true. It's not
necessary to check read permission in nfsv4.
Signed-off-by: Yanchuan Nian
---
fs/nfsd/nfs4state.c | 16 ++--
1
Hi Artem,
Today's linux-next merge of the l2-mtd tree got a conflict in
drivers/mtd/nand/nand_ids.c between commit 5bc7c33ca93a ("mtd: nand:
reintroduce NAND_NO_READRDY as NAND_NEED_READRDY") from the mtd tree and
commits a4c121db7e85 ("mtd: nand_ids: minor clean-ups"), c11138000b6d
("mtd: decommi
于 2013年03月15日 07:43, Russell King - ARM Linux 写道:
> So our wonderful toolchain has decided to start producing NULL warnings
> for every "mcr p15, 0, rX, c7, c10, 4" instruction? I'd just ignore
> them and hope that the toolchain people fix it.
ok, thanks.
:-)
--
Chen Gang
Asianux Corp
于 2013年03月14日 21:25, Jonathan Austin 写道:
>
> You're right that at the moment that suspend code is broken for NOMMU.
>
> However, Will Deacon has a patch to fix it in his nommu branch on
> kernel.org:
>
> https://git.kernel.org/cgit/linux/kernel/git/will/linux.git/commit/?h=nommu
>
> I'll let Wi
On Mon, 2013-03-11 at 17:36 -0400, Mathieu Desnoyers wrote:
> +/*
> + * Do not put head and tail on the same cache-line if concurrent
> + * enqueue/dequeue are expected from many CPUs. This eliminates
> + * false-sharing between enqueue and dequeue.
> + */
> +struct wfcq_head {
> + struct wfcq_
On Thu, Mar 14, 2013 at 5:19 PM, Kim, Milo wrote:
> According to a sysfs documentation(Documentation/filesystem/sysfs.txt),
> scnprintf() should be used in a read operation method.
> It guarantees safe buffer size(PAGE_SIZE) which is allocated by the sysfs.
>
Oh, I missed that. Great, I merged it
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
>
> Here's the second version of the patchset.
>
> The intend of the work is get code ready to enable transparent huge page
> cache for the most simple fs -- ramfs.
>
Where is your git tree including THP cache?
Hillf
--
To unsubscribe fro
On Wednesday, March 13, 2013 4:03 AM, Doug Anderson wrote:
>
> The ehci_vbus_gpio is requested but never freed. This can cause
> problems with deferred probes and would cause problems if
> s5p_ehci_remove was ever called. Use devm to fix this.
>
> Signed-off-by: Doug Anderson
> ---
> drivers/
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
>
> There's only one caller of do_generic_file_read() and the only actor is
> file_read_actor(). No reason to have a callback parameter.
>
This cleanup is not urgent if it nukes no barrier for THP cache.
Hillf
--
To unsubscribe from this
Linus,
I bet if you force the affinity of your perf record to be on
a CPU other than CPU0, you will not get the crash.
This is what I am seeing now. I appears on resume,
CPU0 hotplug callbacks for perf_events are not invoked
leaving DS_AREA MSR to 0.
Can you confirm on your machine?
On Fri, M
在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
> On 03/14, liguang wrote:
> >
> > Signed-off-by: liguang
> > ---
> > kernel/task_work.c |3 ++-
> > 1 files changed, 2 insertions(+), 1 deletions(-)
> >
> > diff --git a/kernel/task_work.c b/kernel/task_work.c
> > index 0bf4258..f458b08 100644
> >
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> From: "Kirill A. Shutemov"
>
> There's only one caller of do_generic_file_read() and the only actor is
> file_read_actor(). No reason to have a callback parameter.
>
This cleanup is not urgent if it nukes no barrier for THP cache.
Hill
On Fri, Mar 15, 2013 at 10:14:41AM +1100, Stephen Rothwell wrote:
> The patch in question has no commit message or headers at all ...
Now fixed. It escaped before I'd finished it...
Alasdair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
The sysfs allocates PAGE_SIZE. It is used by each R/W operation method.
Use it instead of another buffer size.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/power/lp8788-charger.c |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/power/lp8788-charger.c b/drive
According to a sysfs documentation(Documentation/filesystem/sysfs.txt),
scnprintf() should be used in a read operation method.
It guarantees safe buffer size(PAGE_SIZE) which is allocated by the sysfs.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c|3 ++-
drivers/led
The sysfs allocates PAGE_SIZE. It is used by each R/W operation method.
Use it instead of another buffer size.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/video/backlight/lp855x_bl.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/video/backlight/lp855x_bl.c
在 2013-03-14四的 15:40 +0100，Oleg Nesterov写道：
> On 03/14, liguang wrote:
> >
> > Signed-off-by: liguang
>
> Changelog please...
>
OK.
> > ---
> > kernel/task_work.c | 15 +++
> > 1 files changed, 3 insertions(+), 12 deletions(-)
> >
> > diff --git a/kernel/task_work.c b/kernel/ta
On Tue, Mar 12, 2013 at 02:28:11PM -0400, Jean-François Dagenais
(jeff.dagen...@gmail.com) wrote:
> Thoughts?
> /jfd
Well, sounds reasonable.
Please submit patches to Greg Kroah-Hartman , he will
push them upstream.
Acked-by: Evgeniy Polyakov
--
Evgeniy Polyakov
--
To unsubscribe fro
The new context tracking subsystem unconditionally includes kvm_host.h
headers for the guest enter/exit macros. This causes a compile
failure when KVM is not enabled.
Fix by adding an IS_ENABLED(CONFIG_KVM) check to kvm_host so it can
be included/compiled even when KVM is not enabled.
Cc: Freder
cyc_to_sched_clock() is called by sched_clock() and cyc_to_ns()
is called by cyc_to_sched_clock(). I suspect that some compilers
inline both of these functions into sched_clock() and so we've
been getting away without having a notrace marking. It seems that
my compiler isn't inlining cyc_to_sched_c
On 14.03.2013 22:33, Alan Stern wrote:
On Thu, 14 Mar 2013, Soeren Moch wrote:
If the memory really is being leaked here in some sort of systematic
way, we may be able to see it in your debugging output after a few
seconds.
OK, here are the first seconds of the log. But the buffer exhaustion
The ehci_vbus_gpio is requested but never freed. This can cause
problems with deferred probes and would cause problems if
s5p_ehci_remove was ever called. Use devm to fix this.
Signed-off-by: Doug Anderson
---
drivers/usb/host/ehci-s5p.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
On Thu, Mar 14, 2013 at 12:38:00PM +0800, Chen Gang wrote:
> Hello Maintainers:
>
> are these warnings for head.S OK ?
>
>
> make:
> make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
> (this time, CONFIG_MMU=y)
>
> warning information:
> arch/arm/boot/compressed/head.S: Assembler messages:
On Thu, Mar 14, 2013 at 03:46:51PM -0700, Andrew Morton wrote:
> On Wed, 13 Mar 2013 22:02:16 +0100 Jan Kara wrote:
>
> > > > ... remembering why we need to get to sb and why ext3 needs this ... So
> > > > maybe a better solution would be to have a bio flag meaning that pages
> > > > need
> > >
On Thu, 2013-03-14 at 16:15 -0700, dormando wrote:
> *sigh*. it's been a long month, sorry:
>
> [58377.436522] IPv4: Attempt to release TCP socket family 2 in state 1
> 8813fbad9500
> [58377.436539] [ cut here ]
> [58377.436545] WARNING: at net/ipv4/af_inet.c:146
> ine
> On Thu, 2013-03-14 at 14:21 -0700, dormando wrote:
> > >
> > > diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> > > index 68f6a94..1d4d97e 100644
> > > --- a/net/ipv4/af_inet.c
> > > +++ b/net/ipv4/af_inet.c
> > > @@ -141,8 +141,9 @@ void inet_sock_destruct(struct sock *sk)
> > > sk_mem_r
Hi Alasdair,
While importing the device-mapper quilt series, I got this error:
$ git am
../quilt/device-mapper/dm-cache-policy-fix-description-of-lookup-fn.patch
Patch format detection failed.
The patch in question has no commit message or headers at all ...
I did this:
@@ -1,3 +1,6 @@
+From:
On Thu, Mar 14, 2013 at 11:53 PM, Stephane Eranian wrote:
> On Thu, Mar 14, 2013 at 11:42 PM, Stephane Eranian wrote:
>> On Thu, Mar 14, 2013 at 11:19 PM, Stephane Eranian
>> wrote:
>>> On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds
>>> wrote:
On Thu, Mar 14, 2013 at 3:09 PM, Stephane E
On Thu, Mar 14, 2013 at 10:24 PM, Toralf Förster wrote:
> On 03/14/2013 10:21 PM, Dave Jones wrote:
>> hah, strndup_user taking a signed long instead of a size_t as it's length
>> arg.
>>
>> either it needs to change, or it needs an explicit check for < 1
>>
>> I wonder how many other paths make
I believe these error messages are already logged
on allocation failure by warn_alloc_failed and so
get a dump_stack on OOM.
Remove the unnecessary additional error logging.
Around these deletions:
o Alignment neatening.
o Remove unnecessary casts of dma_alloc_coherent.
o Hoist assigns from ifs.
Hi,
We use genalloc for managing certain pools of physical memory. genalloc
currently uses unsigned long for virtual addresses and phys_addr_t for
physical addresses. Our ARM LPAE systems have 64-bit physical addresses
but unsigned long is still 32 bits. Using gen_pool_add breaks with
addres
On Wednesday 13 March 2013, Nicolas Ferre wrote:
> In case we end-up with an agreement on the path those fixes should
> follow, here is the location of my updated material rebased on top of 3.9-rc2:
>
> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>
> Linux 3.9-r
PF_THREAD_BOUND was originally used to mark kernel threads which were
bound to a specific CPU using kthread_bind() and a task with the flag
set allows cpus_allowed modifications only to itself. Workqueue is
currently abusing it to prevent userland from meddling with
cpus_allowed of workqueue worke
Make worker_ida an idr - worker_idr and use it to implement
for_each_pool_worker() which will be used to simplify worker rebinding
on CPU_ONLINE.
pool->worker_idr is protected by both pool->manager_mutex and
pool->lock so that it can be iterated while holding either lock.
* create_worker() alloca
rebind_workers() will be reimplemented in a way which makes it mostly
decoupled from the rest of worker management. Move rebind_workers()
so that it's located with other CPU hotplug related functions.
This patch is pure function relocation.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 142
Hello,
per-cpu worker rebinding on CPU_ONLINE has always been complex. A lot
of the complexity comes from the fact that CPU_ONLINE should ask each
worker, which may be in any state, to rebind itself. With recent
patch to replace PF_THREAD_BOUND with PF_NO_SETAFFINITY (the patch is
pending and in
Vivek,
On Wed, Mar 13, 2013 at 11:22 PM, Vivek Gautam
wrote:
> It will be nice if you can please update relevant information
> alongwith this, in the bindings doc for "exynos-usb".
Sure. It always feels like device tree additions ought to be separate
patches from bindings patches, so I'll just
Rebinding workers of a per-cpu pool after a CPU comes online involves
a lot of back-and-forth mostly because only the task itself could
adjust CPU affinity if PF_THREAD_BOUND was set.
As CPU_ONLINE itself couldn't adjust affinity, it had to somehow
coerce the workers themselves to perform set_cpus
With the recent addition of the custom attributes support, unbound
pools may have allowed cpumask which isn't full. As long as some of
CPUs in the cpumask are online, its workers will maintain cpus_allowed
as set on worker creation; however, once no online CPU is left in
cpus_allowed, the schedule
The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
using the common clock framework. Document it.
Signed-off-by: Doug Anderson
---
Documentation/devicetree/bindings/usb/exynos-usb.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bind
On Thu, 14 Mar 2013 15:42:43 -0700 "Darrick J. Wong"
wrote:
> Subject: [PATCH] mm: Make snapshotting pages for stable writes a per-bio
> operation
>
> Walking a bio's page mappings has proved problematic, so create a new bio flag
> to indicate that a bio's data needs to be snapshotted in order
On Thursday 14 March 2013, Nicolas Ferre wrote:
> Here is a little pull-request for 3.9-rc (I guess it if -rc4 now that
> you've just sent the one for -rc3).
>
> I have other material but it is related to the AT91 framebuffer and we are
> currently discussing it so I hold them back for now.
>
> T
On Thu, Mar 14, 2013 at 11:37:50AM +0100, Miklos Szeredi wrote:
> > As for whiteouts... I think we ought to pull these bits of unionmoun
> > queue into the common stem and add the missing filesystems to them;
> > ext* and ufs are trivial (keep in mind that FFS derivatives, including
> > ext*, have
On Thu, 2013-03-14 at 14:21 -0700, dormando wrote:
> >
> > diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> > index 68f6a94..1d4d97e 100644
> > --- a/net/ipv4/af_inet.c
> > +++ b/net/ipv4/af_inet.c
> > @@ -141,8 +141,9 @@ void inet_sock_destruct(struct sock *sk)
> > sk_mem_reclaim(sk);
>
PF_THREAD_BOUND was originally used to mark kernel threads which were
bound to a specific CPU using kthread_bind() and a task with the flag
set allows cpus_allowed modifications only to itself. Workqueue is
currently abusing it to prevent userland from meddling with
cpus_allowed of workqueue worke
On Thu, Mar 14, 2013 at 11:42 PM, Stephane Eranian wrote:
> On Thu, Mar 14, 2013 at 11:19 PM, Stephane Eranian wrote:
>> On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds
>> wrote:
>>> On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian
>>> wrote:
Could be related to suspend/resume. But
On Thu, Mar 14, 2013 at 03:20:05PM -0700, Greg KH wrote:
> On Thu, Mar 14, 2013 at 05:10:40PM -0400, Boris Ostrovsky wrote:
> > Use helper function instead of an array to report whether register
> > bank is shared. Currently only bank 4 (northbridge) is shared.
> >
> > Signed-off-by: Boris Ostrovs
On Wed, 13 Mar 2013 22:02:16 +0100 Jan Kara wrote:
> > > ... remembering why we need to get to sb and why ext3 needs this ... So
> > > maybe a better solution would be to have a bio flag meaning that pages
> > > need
> > > bouncing? And we would set it from filesystems that need it - in case of
On Thu, Mar 14, 2013 at 6:34 PM, Frederic Weisbecker wrote:
> 2013/3/14 Paul Gortmaker :
>> On Thu, Mar 14, 2013 at 4:39 PM, Andrew Morton
>> wrote:
>>> On Thu, 14 Mar 2013 15:26:29 +0100 Frederic Weisbecker
>>> wrote:
>>>
wake_up_klogd() is useless when CONFIG_PRINTK=n because
neithe
On Wed, Mar 13, 2013 at 10:02:16PM +0100, Jan Kara wrote:
> On Wed 13-03-13 12:44:29, Darrick J. Wong wrote:
> > On Wed, Mar 13, 2013 at 09:50:21AM +0100, Jan Kara wrote:
> > > On Tue 12-03-13 18:10:20, Darrick J. Wong wrote:
> > > > On Tue, Mar 12, 2013 at 03:32:21PM -0700, Andrew Morton wrote:
>
On Thu, Mar 14, 2013 at 11:19 PM, Stephane Eranian wrote:
> On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds
> wrote:
>> On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian wrote:
>>>
>>> Could be related to suspend/resume. But were you running perf across
>>> that resume/suspend cycle?
>>
>> No.
2013/3/14 Paul Gortmaker :
> On Thu, Mar 14, 2013 at 4:39 PM, Andrew Morton
> wrote:
>> On Thu, 14 Mar 2013 15:26:29 +0100 Frederic Weisbecker
>> wrote:
>>
>>> wake_up_klogd() is useless when CONFIG_PRINTK=n because
>>> neither printk() nor printk_sched() are in use and there
>>> are actually no
On Wed, 13 Mar 2013 18:47:05 +0100 Oleg Nesterov wrote:
> orderly_poweroff() can be used from any context but UMH_WAIT_EXEC
> is sleepable. Move the "force" logic into __orderly_poweroff() and
> change orderly_poweroff() to use the global poweroff_work which
> simply calls __orderly_poweroff().
>
Including libio.h causes build failures on uClibc systems (which lack
libio.h).
It appears that libio.h was only included to pull in a definition for
NULL, so it has been replaced by stddef.h.
On powerpc, libio.h was conditionally included, but could be removed
completely as it is unneeded. Also,
On Thu, 14 Mar 2013, Arnd Bergmann wrote:
> The platform was merged about 10 years ago, and has seen few updates
> for most of the time since. The people that merged the code seem
> no longer interested in it either, so let's remove it now.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Thomas Glei
Hello,
On Thu, 14 Mar 2013 21:36:24 +0100
Arkadiusz Miskiewicz wrote:
> After upgrading from 3.8.2 to 3.8.3 I'm getting regression :
[...]
> 2a9810441fcc26cf3f006f015f8a62094fe57a90 is the first bad commit
I also have an 3.8.2->3.8.3 regression which goes away with reverting
the same patch - X
On Thu, Mar 14, 2013 at 4:39 PM, Andrew Morton
wrote:
> On Thu, 14 Mar 2013 15:26:29 +0100 Frederic Weisbecker
> wrote:
>
>> wake_up_klogd() is useless when CONFIG_PRINTK=n because
>> neither printk() nor printk_sched() are in use and there
>> are actually no waiter on log_wait waitqueue. It sho
2013/3/14 Andrew Morton :
> On Thu, 14 Mar 2013 15:26:29 +0100 Frederic Weisbecker
> wrote:
>
>> wake_up_klogd() is useless when CONFIG_PRINTK=n because
>> neither printk() nor printk_sched() are in use and there
>> are actually no waiter on log_wait waitqueue. It should
>> be a stub in this case
On Thu, Mar 14, 2013 at 05:10:40PM -0400, Boris Ostrovsky wrote:
> Use helper function instead of an array to report whether register
> bank is shared. Currently only bank 4 (northbridge) is shared.
>
> Signed-off-by: Boris Ostrovsky
> ---
> arch/x86/kernel/cpu/mcheck/mce_amd.c | 17 +---
On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds
wrote:
> On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian wrote:
>>
>> Could be related to suspend/resume. But were you running perf across
>> that resume/suspend cycle?
>
> No.
>
> In most cases I was running a perf record before and after (but n
On Thu, Mar 14, 2013 at 11:12:21PM +0100, Paul Bolle wrote:
> On Thu, 2013-03-14 at 15:02 -0700, Greg Kroah-Hartman wrote:
> > On Thu, Mar 14, 2013 at 12:09:53PM +0100, Paul Bolle wrote:
> > > Well, now that you somehow managed to review this patch the urge to
> > > clean this line up has suddenly
On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian wrote:
>
> Could be related to suspend/resume. But were you running perf across
> that resume/suspend cycle?
No.
In most cases I was running a perf record before and after (but not
*while* suspending)
In at least one other crash, I didn't run pe
On Fri, Mar 08, 2013 at 11:29:15PM +0100, Jiri Slaby wrote:
> On 03/08/2013 11:01 PM, Jiri Slaby wrote:
> > Hi,
> >
> > Tony Jones found that the following commit:
> > perf: Fix parsing of __print_flags() in TP_printk()
> > is applied to 3.0 twice.
> >
> > Once as:
> > commit 248f3235861683bb1f
With the Cortina Gemini platform gone, nothing in ARM uses
the Faraday 526 CPU core support any more. There is at least
one other platform using this (Moschip MCS814x), but the
efforts to get that merged into mainline appear to have
stalled.
If someone still needs this code, please speak up now,
o
The l7200 platform was removed in 2.6.35, but one file came
back due to a failed merge conflict resolution. Let's kill
it again.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-l7200/include/mach/debug-macro.S | 38 --
1 file changed, 38 deletions(-)
delete mode 100644 ar
Currently number of error reporting register banks is hardcoded to
6 on AMD processors. This may break in virtualized scenarios when
a hypervisor prefers to report fewer banks than what the physical
HW provides.
Since number of supported banks is reported in MSR_IA32_MCG_CAP[7:0]
that's what we sh
The gemini platform has not seen any updates from its
maintainer since 2010, and has no defconfig file, which
has lead to bitrot in a number of places:
* System restart has been broken for a long time despite
repeated attempts from Russell to get the obvious
fix at least acknowledged by someon
The h720x platform support is going away in linux-3.10, so the
MTD driver will also not be needed any more.
Signed-off-by: Arnd Bergmann
Cc: linux-...@lists.infradead.org
Cc: Artem Bityutskiy
Cc: David Woodhouse
---
drivers/mtd/maps/Kconfig | 7 ---
drivers/mtd/maps/Makefile | 1
There is no defconfig file for gemini, which has lead to a lot
of bitrot. This makes the broken board files, the gpio implementation
and the reset logic work again, and fixes the build warnings
that got introduced with the changes to the readl/writel prototypes.
Signed-off-by: Arnd Bergmann
---
The platform was merged about 10 years ago, and has seen few updates
for most of the time since. The people that merged the code seem
no longer interested in it either, so let's remove it now.
Signed-off-by: Arnd Bergmann
Cc: Thomas Gleixner
Cc: Robert Schwebel
Cc: Sascha Hauer
---
arch/arm/K
We have discussed cleaning these up before, but we never actually
removed them. For all I can tell, none of these have any users
in the upstream kernel, so they can be removed. If you know of
anyone using them, please yell now, or send a revert patch
later if you really want them back.
Arnd Bergma
On Thu, 2013-03-14 at 15:02 -0700, Greg Kroah-Hartman wrote:
> On Thu, Mar 14, 2013 at 12:09:53PM +0100, Paul Bolle wrote:
> > Well, now that you somehow managed to review this patch the urge to
> > clean this line up has suddenly diminished. But maybe you're lucky and
> > this will not pass Greg.
Use helper function instead of an array to report whether register
bank is shared. Currently only bank 4 (northbridge) is shared.
Signed-off-by: Boris Ostrovsky
---
arch/x86/kernel/cpu/mcheck/mce_amd.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/arch/x86
Boris,
Here is the updated patch for determining number of regiter banks on
AMD plus a patch removing shared_bank array, as you suggested.
Offline/online testing didn't show any issues.
Boris Ostrovsky (2):
x86/mce: Replace shared_bank array with is_shared_bank() helper
x86/mce: Use MCG_C
Hi,
On Thu, Mar 14, 2013 at 10:06 PM, Linus Torvalds
wrote:
>
> On Thu, Mar 14, 2013 at 1:32 PM, Linus Torvalds
> wrote:
> >
> > And to make things interesting, I seem to be able to only reproduce
> > this *after* a suspend cycle. That may be just happenstance, since it
> > seemed to be hard to
On Sun, 3 Mar 2013 13:49:13 -0500 Phillip Susi wrote:
> Any partitions added by user space to the loop device were being
> left in place after detaching the loop device. This was because
> the detach path issued a BLKRRPART to clean up partitions if
> LO_FLAGS_PARTSCAN was set, meaning that the
On Thu, Mar 14, 2013 at 12:09:53PM +0100, Paul Bolle wrote:
> On Thu, 2013-03-14 at 13:59 +0300, Dan Carpenter wrote:
> > Your patch is fine as is, but if you wanted to send a follow on
> > patch to break the depend mess into separate lines, that would also
> > be welcome. :)
>
> Well, now that y
gcc-4.7 and higher add a lot of false positive warnings about
potential uses of uninitialized warnings, but only when optimizing
for size (-Os). This is the default when building allyesconfig,
which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.
In order to avoid getting a lot of patches that initialize su
The ab8500 device is a child of the prcmu device, which is a memory mapped
bus device, whose children are addressable using physical memory addresses,
not using mailboxes, so a mailbox number in the ab8500 node cannot be
parsed by DT. Nothing uses this number, since it was only introduced
as part o
From: Axel Lin
This patch fixes below build error when CONFIG_POWER_SUPPLY is not set.
drivers/built-in.o: In function `ab8500_power_off':
drivers/mfd/ab8500-sysctrl.c:37: undefined reference to
`power_supply_get_by_name'
drivers/mfd/ab8500-sysctrl.c:53: undefined reference to
`power_supply_ge
The automated ARM build tests have shown that the tulip de4x5 driver
uses the old-style virt_to_bus() interface on some architectures.
Alpha, Sparc and PowerPC did not hit this problem, because they
use a different code path, and most other architectures actually
do provide VIRT_TO_BUS.
Signed-of
This driver can be enabled on OMAP1 at the moment, which breaks
allyesconfig for that platform. Let's mark it OMAP2PLUS-only
in Kconfig, since that is the only thing it builds on.
Signed-off-by: Arnd Bergmann
Cc: Mauro Carvalho Chehab
Cc: Timo Kokkonen
Cc: Tony Lindgren
Cc: Laurent Pinchart
C
The vfio drivers call kmalloc or kzalloc, but do not
include , which causes build errors on
ARM.
Signed-off-by: Arnd Bergmann
Cc: Alex Williamson
Cc: k...@vger.kernel.org
---
Please apply for 3.9
drivers/vfio/pci/vfio_pci_config.c | 1 +
drivers/vfio/pci/vfio_pci_intrs.c | 1 +
2 files change
4740f73fe5 "mfd: remove use of __devexit" removed the __devexit annotation
on the twl4030_madc_remove function, but left an __exit_p() present on the
pointer to this function. Using __exit_p was as wrong with the devexit in
place as it is now, but now we get a gcc warning about an unused function.
Disabling CONFIG_VIRT_TO_BUS on ARM showed that the hisax netjet
driver depends on this deprecated functionality but is not
marked so in Kconfig.
Rather than adding ARM to the already long list of architectures
that this driver is broken on, this patch adds 'depends on
VIRT_TO_BUS' and removes the
The resource ID used for VM socket control packets (0) is already
used for the VMCI_GET_CONTEXT_ID hypercall so a new ID (15) must be
used when the guest sends these datagrams to the hypervisor.
The hypervisor context ID must also be removed from the internal
blacklist.
Signed-off-by: Reilly Gran
From: "Steven Rostedt (Red Hat)"
The latency tracers require the buffers to be in overwrite mode,
otherwise they get screwed up. Force the buffers to stay in overwrite
mode when latency tracers are enabled.
Added a flag_changed() method to the tracer structure to allow
the tracers to see what fl
From: "Steven Rostedt (Red Hat)"
Changing the overwrite mode for the ring buffer via the trace
option only sets the normal buffer. But the snapshot buffer could
swap with it, and then the snapshot would be in non overwrite mode
and the normal buffer would be in overwrite mode, even though the
opt
From: "Steven Rostedt (Red Hat)"
Seems that the tracer flags have never been protected from
synchronous writes. Luckily, admins don't usually modify the
tracing flags via two different tasks. But if scripts were to
be used to modify them, then they could get corrupted.
Move the trace_types_lock
101 - 200 of 763 matches
Mail list logo
