iohook is a driver that exports sysfs interfaces used to talk to the IO Hook
in the kernel in order to emulate h/w events. Here's how it works:
The sysfs interfaces can be used to add/delete Register Overrides with user-
defined values. The user can also specify which IRQ to be triggered via
Inter
The following kernel functions are exported:
hook_add_ovrd
hook_query_ovrd
hook_cleanup_ovrd
hook_start_ovrd
hook_stop_ovrd
hook_get_status
Kernel modules can use them to add/delete/query Register Overrides, and
to start/stop the hook engine.
Signed-
Hi Bjorn,
This was originally the method I used to test hotplug on Intel SDV machines
which are not capable of doing hotplug. I would like to present it here in
case it interests the community, then it can be made available to a wider
range of developers who are working on hotplug.
I used it to g
This patch provides a hook in the core h/w access functions in the kernel.
It also introduces Register Override, which is a set of bits defined in RAM
to override the real value of a h/w register. With the hook in place, access
to h/w registers can be redirected to Register Overrides with user-defi
2013/7/26 Dilger, Andreas :
> On 2013/07/25 1:06 AM, "Xiong Zhou" wrote:
>
>>From: Xiong Zhou
>>
>>Add BLOCK depends in Kconfig for LUSTRE to fix this:
>>drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2
>>:
>>error: implicit declaration of function ʽunregister_blkdevʼ
>>
Hi,
On Fri, 2013-07-26 at 02:06 +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Thursday, July 25, 2013 1:52 PM
> >
> > On Thu, Jul 25, 2013 at 07:46:58PM +, Paul Zimmerman wrote:
> > > > diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> > >
Dave,
All comments are good to me, and will be applied to next version, thanks a lot.
On Fri, Jul 26, 2013 at 10:50 AM, Dave Chinner wrote:
> On Thu, Jul 25, 2013 at 04:23:39PM +0800, zwu.ker...@gmail.com wrote:
>> From: Zhi Yong Wu
>>
>> It can take a long time to run log recovery operation
On Thu, 25 Jul 2013 20:10:59 +0100
Mark Brown wrote:
> On Thu, Jul 25, 2013 at 11:13:57AM +0200, Jean-Francois Moine wrote:
> > The function kirkwood_i2s_dev_remove() may be used when probe fails.
>
> This seems fine but doesn't apply against current code but otherwise
> seems fine.
My base is
On Thu, 25 Jul 2013 19:23:56 +0100
Mark Brown wrote:
> On Thu, Jul 25, 2013 at 10:38:55AM +0100, Russell King - ARM Linux wrote:
>
> > There's a much better solution to this, which is to get rid of
> > kirkwood_dma_priv entirely:
>
> This does seem a lot nicer, can we either grab the relevant p
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/xillybus/xillybus_pcie.o:(.data+0x6d8): multiple definition of
`xillyname'
drivers/staging/xillybus/xillybus_core.o:(.data+0x888): first defined here
Caused by commit 48bae0
2013/7/25 Paul Bolle :
> On Thu, 2013-07-25 at 15:06 +0800, Xiong Zhou wrote:
>> Add BLOCK depends in Kconfig for LUSTRE to fix this:
>> drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2:
>> error: implicit declaration of function ‘unregister_blkdev’
>>
>> Signed-off-by: Xi
No, it still raised the same assertion as below:
[ 521.715103] XFS: Assertion failed: !(bip->bli_item.li_flags &
XFS_LI_IN_AIL), file: fs/xfs/xfs_buf_item.c, line: 940
[ 521.716378] [ cut here ]
[ 521.716934] kernel BUG at fs/xfs/xfs_message.c:108!
[ 521.717364] invalid
2013/7/18 Felipe Balbi :
> On Thu, Jul 18, 2013 at 05:28:19PM +0800, Rong Wang wrote:
>> Hi Felipe,
>>
>> Thanks, I'll test the patch.
>>
>> But sysfs_notify(&gadget->dev.kobj, NULL, "status"), status or state ?
>> I notice that DEVICE_ATTR(state, S_IRUGO, usb_gadget_state_show, NULL)
>
> good eyes
At Thu, 25 Jul 2013 11:53:25 -0700,
Joe Perches wrote:
>
>
> Using 0x%# emits 0x0x. Only one is necessary.
>
> Signed-off-by: Joe Perches
Acked-by: Takashi Iwai
thanks,
Takashi
> ---
> arch/parisc/kernel/signal.c | 2 +-
> drivers/clocksource/acpi_pm.c | 4 ++--
> drivers/net/
Thanks, Gerhard.
I'll improve the code and return with the third version.
Best regards,
Alexander.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Pl
On Fri, Jul 26, 2013 at 04:58:14AM +, Zhu Richard-R65037 wrote:
> Hi Shawn:
> yes, it is.
>
> BTW, Should I re-send the AHCI_IMX patch-set or send out one stand-alone
> patch to fix this issue?
>
I think an incremental fixing patch is good.
Shawn
--
To unsubscribe from this list: send the
This patch hooks into the existing broadcast framework with the support that
this
patchset introduces for ppc, and the cpuidle driver backend
for powernv(posted out recently by Deepthi Dharwar) to add sleep state as
one of the deep idle states, in which the decrementer is switched off.
However in
On Thu, Jul 25, 2013 at 11:44:50PM +, Daniel Phillips wrote:
> Hi Willy,
>
> I understand completely. I don't blame you. Filter the thread. Done.
So because people speak loudly at night below my window in summer, I
have to close the window and install a fan to get some air ? And all
the neigh
On ppc, in deep idle states, the local clock event device of CPUs gets
switched off. On PowerPC, the local clock event device is called the
decrementer. Make use of the broadcast framework to issue interrupts to
cpus in deep idle states on their timer events, except that on ppc, we
do not have an e
From: Srivatsa S. Bhat
For scalability and performance reasons, we want the broadcast timer
interrupts to be handled as efficiently as possible. Fixed IPI messages
are one of the most efficient mechanisms available - they are faster
than the smp_call_function mechanism because the IPI handlers ar
On PowerPC, when CPUs enter deep idle states, their local timers are
switched off. The responsibility of waking them up at their next timer event,
needs to be handed over to an external device. On PowerPC, we do not have an
external device equivalent to HPET, which is currently done on architecture
From: Srivatsa S. Bhat
The IPI handlers for both PPC_MSG_CALL_FUNC and PPC_MSG_CALL_FUNC_SINGLE
map to a common implementation - generic_smp_call_function_single_interrupt().
So, we can consolidate them and save one of the IPI message slots, (which are
precious, since only 4 of those slots are av
Hi Shawn:
yes, it is.
BTW, Should I re-send the AHCI_IMX patch-set or send out one stand-alone patch
to fix this issue?
Hi Tejun:
What's your opinion?
Best Regards
Richard Zhu
-Original Message-
From: Shawn Guo [mailto:shawn@linaro.org]
Sent: Friday, July 26, 2013 12:04 PM
To: Zh
Hi Linus,
On Tue, Jul 16, 2013 at 6:55 PM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> Select PINCTRL_ADI2 for bf54x and bf60x by default.
>
> Signed-off-by: Sonic Zhang
> ---
> arch/blackfin/Kconfig | 7 +
> arch/blackfin/include/asm/portmux.h | 14 +-
>
Hi Linus,
On Tue, Jul 16, 2013 at 6:55 PM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> - Remove non gpio lib code from blackfin architecture.
> - Limit the lagecy blackfin gpio driver to bf5xx processors only.
> - Remove unused definition of the pint power functions.
>
> Signed-off-by: Sonic Zhan
Hi Linus,
On Tue, Jul 16, 2013 at 6:55 PM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> The new ADI GPIO2 controller was introduced since the BF548 and BF60x
> processors. It differs a lot from the old one on BF5xx processors. So,
> create a pinctrl driver under pinctrl framework.
>
> - Define g
On Thu, Jul 25, 2013 at 03:37:53PM -0600, Jason Gunthorpe wrote:
> We use DT has a kernel configuration input. Our environment is
> designed to guarantee 100% that the kernel and DT match exactly. DT
> very deliberately isn't an ABI boundary in our systems.
It is nice that you use DT in that way,
-> The ledptrs[] array is never initialized.
-> There is no place where kbd->ledmode is set to LED_SHOW_MEM therefore the if
statement does not make much sense.
-> Since LED_SHOW_MEM is not used, it can be removed from the header file as
well.
Signed-off-by: Andreas Platschek
---
drivers/tty
Hi Antonios,
On 25 July 2013 21:04, Antonios Motakis
wrote:
> IOMMU groups are expected by certain users of the IOMMU API,
> e.g. VFIO. Since each device is behind its own System MMU, we
> can allocate a new IOMMU group for each device.
>
> This patch depends on Cho KyongHo's patch series titled
On Thu, Jul 25, 2013 at 11:53:49AM -0700, Stephen Warren wrote:
> On 07/25/2013 11:48 AM, Richard Cochran wrote:
> > On Thu, Jul 25, 2013 at 07:29:20PM +0100, Mark Rutland wrote:
> >>
> >> As long as we can make sufficiently clear that trying to use an unstable
> >> binding is going to be *very* pa
On Thu, Jul 25, 2013 at 09:17:01AM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Wed, 2013-07-24 at 12:47 +1000, Dave Chinner wrote:
> > On Tue, Jul 23, 2013 at 02:58:58PM -0700, Jeremy Allison wrote:
> > > Having said that the OEMs that are using it does
> > > find it improves write speeds by a la
On 25.07.2013 21:47, Rafael J. Wysocki wrote:
Other people who experienced problems with backlight in 3.11-rc2, please let me
know whether or not the revert works for you too if you can.
Before reverting the patch /sys/class/backlight was empty and backlight
brightness was set to max, now it
On Wed, Jul 24, 2013 at 10:37 AM, Stephen Boyd wrote:
> [snip]
> + unsigned int i, divisor;
> + const struct msm_baud_map *entry;
> + static const struct msm_baud_map table[] = {
> + { 1536, 0x00, 1 },
> + { 768, 0x11, 1 },
> + { 384,
I guess my signed off got stripped somewhere. Originally I maintained those
commits but Steve Dickson from red hat picked them up and they then made it
into trond's tree and then into Linus'.
I unfortunately don't have my davequigley.com identities on my iPhone but you
can add a sign off by dpq
On Thu, 25 Jul 2013, Michael Ellerman wrote:
> On Tue, Jul 23, 2013 at 05:38:21PM -0400, Vince Weaver wrote:
>
> Well cursing is what witches do, but if you need someone to swear a bit
> I can help you out, I am fuckin Australian after all.
I should point out the cursing is directed at the code i
Hi Frederic,
I apologise for the confusion. As Paul pointed out maybe the usage of
the term lapic is causing a large amount of confusion. So please see the
clarification below. Maybe it will help answer your question.
On 07/26/2013 08:09 AM, Preeti U Murthy wrote:
> Hi Frederic,
>
> On 07/25/201
On 07/19/2013 02:57:18 PM, Andrew Morton wrote:
On Tue, 16 Jul 2013 16:45:39 -0700 (PDT) Rob Landley
wrote:
> Command line option rootfstype=ramfs to obtain old initramfs
behavior,
> and use ramfs instead of tmpfs for stub when root= defined (for
cosmetic
> reasons).
Could we get a Docu
The usage of strict_strto*() is not preferred, because
strict_strto*() is obsolete. Thus, kstrto*() should be
used.
Signed-off-by: Jingoo Han
---
Changes since v1:
- mechanically replaced strict_strto*() with kstrto*().
drivers/base/core.c |2 +-
drivers/base/memory.c
Hi Paul,
After merging the lblnet tree, today's linux-next build (x86_64
allmodconfig) failed like this:
security/selinux/hooks.c: In function 'sb_finish_set_opts':
security/selinux/hooks.c:448:19: error: 'SE_SBLABELSUPP' undeclared (first use
in this function)
sbsec->flags |= SE_SBLABELSUPP;
On Fri, Jul 26, 2013 at 03:46:42AM +, Zhu Richard-R65037 wrote:
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: Friday, July 26, 2013 2:32 AM
> To: Stephen Rothwell
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel
Hi Randy:
Thanks for your kindly reminder.
I re-produced this issue at my side.
Now, I'm trying to find a proper method to fix it.
Best Regards
Richard Zhu
-Original Message-
From: Randy Dunlap [mailto:rdun...@infradead.org]
Sent: Friday, July 26, 2013 2:32 AM
To: Stephen Rothwell
Cc: l
On Wed, 24 Jul 2013, Andi Kleen wrote:
> Sorry I meant flags as an alias of "the 64bits currently occupied by the
> bitfield". Perhaps the name choice was not very good.
>
> "flags_bitfield" ?
>
> So the tool would only need to know that, not every bit.
>
> In theory it could be also generalize
On 07/25/2013 11:05 PM, Tejun Heo wrote:
Hello, Tang.
On Thu, Jul 25, 2013 at 12:09:29PM +0800, Tang Chen wrote:
And as in [patch 14/21], when reserving hotpluggable memory, we use
pxm. So my
Which is kinda nasty.
Yes, will remove it.
idea was to do a nid sync in numa_init(). After this
On 07/25/2013 11:09 PM, Tejun Heo wrote:
Hello, Tang.
On Thu, Jul 25, 2013 at 11:50:12AM +0800, Tang Chen wrote:
movablecore boot option was used to specify the size of ZONE_MOVABLE. And
this patch-set aims to arrange ZONE_MOVABLE with SRAT info. So my original
thinking is to reuse movablecore.
On Thu, Jul 25, 2013 at 3:58 PM, Geert Uytterhoeven
wrote:
> On Wed, Jan 11, 2012 at 9:22 PM, Grant Likely
> wrote:
>> NO_IRQ is evil. Stop using it in arch/powerpc and powerpc device drivers
>
>> diff --git a/sound/soc/fsl/fsl_ssi.c b/sound/soc/fsl/fsl_ssi.c
>> index 3e06696..55c6ff9 100644
>>
Hi Eric,
Today's linux-next merge of the selinux tree got a conflict in
security/selinux/hooks.c between commit eb9ae686507b ("SELinux: Add new
labeling type native labels") from Linus' tree and commits 40d3d0b85fa2
("SELinux: remove crazy contortions around proc") and a64c54cf0811
("SELinux: pass
On Fri, Jul 19, 2013 at 04:21:28PM +0900, Jingoo Han wrote:, Jingoo Han wrote:
>
> The usage of strict_strto*() is not preferred, because
> strict_strto*() is obsolete. Thus, kstrto*() should be
> used.
>
> Signed-off-by: Jingoo Han
> ---
> drivers/base/core.c |2 +-
> driv
On 07/25/2013 11:17 PM, Tejun Heo wrote:
Hello,
On Thu, Jul 25, 2013 at 10:13:21AM +0800, Tang Chen wrote:
This is rather hacky. Why not just introduce MEMBLOCK_NO_MERGE flag?
The original thinking is to merge regions with the same nid. So I used pxm.
And then refresh the nid field when nids
On 07/26/2013 11:07 AM, Tejun Heo wrote:
> Hello,
>
> On Fri, Jul 26, 2013 at 10:13:25AM +0800, Lai Jiangshan wrote:
>>> Hmmm... if I'm not confused, now the cpu pools just behave like a
>>> normal unbound pool when the cpu goes down,
>>
>> cpu pools are always referenced, they don't behave like u
Hi Paul,
On 07/26/2013 08:49 AM, Paul Mackerras wrote:
> On Fri, Jul 26, 2013 at 08:09:23AM +0530, Preeti U Murthy wrote:
>> Hi Frederic,
>>
>> On 07/25/2013 07:00 PM, Frederic Weisbecker wrote:
>>> Hi Preeti,
>>>
>>> I'm not exactly sure why you can't enter the broadcast CPU in dynticks idle
>>>
On 07/24/2013 06:19 PM, Nicholas A. Bellinger wrote:
Because -fb has had close to zero peer review, and you've not solicited
much input (none from us) before making significant changes to
rtslib/targetcli over the past 1 1/2 years.
For your own private tree this wouldn't matter. However, for a
On 07/25/2013 07:14 PM, Jesse Barnes wrote:
> To clarify: it'll either be marked reserved or not listed at all in e820,
> which is why I did this early, before any other e820 stuff like the "RAM
> buffer" are allocated, and before we could use the iomem resource (or maybe
> we could even early p
On Thu, 25 Jul 2013, Peter Zijlstra wrote:
> On Thu, Jul 25, 2013 at 08:34:51AM -0400, Vince Weaver wrote:
> > Yes, I meant the addition of the sample_id fields to the existing sample
> > values. Though if Peter is right and those have always been there since
> > the beginning and just not docu
On Thu, 2013-07-25 at 14:59 -0400, Steven Rostedt wrote:
> Now that I know what's the problem, it shouldn't be too hard to fix.
It was a bit more involved to fix than I expected. I don't like the fact
that if you filter on only module functions and remove that module, you
now remove the filter an
On Fri, Jul 26, 2013 at 08:09:23AM +0530, Preeti U Murthy wrote:
> Hi Frederic,
>
> On 07/25/2013 07:00 PM, Frederic Weisbecker wrote:
> > Hi Preeti,
> >
> > I'm not exactly sure why you can't enter the broadcast CPU in dynticks idle
> > mode.
> > I read in the previous patch that's because in d
On Thu, 25 Jul 2013, Adrian Hunter wrote:
> >> diff --git a/include/uapi/linux/perf_event.h
> >> b/include/uapi/linux/perf_event.h
> >> index 0b1df41..00d8274 100644
> >> --- a/include/uapi/linux/perf_event.h
> >> +++ b/include/uapi/linux/perf_event.h
> >> @@ -478,6 +478,16 @@ enum perf_event_ty
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_pm.c between commit 14c5cec5d0cd ("drm/i915:
initialize gt_lock early with other spin locks") from the drm-intel-fixes
tree and commit 907b28c56ea4 ("drm/i915: Colocate all GT access routines
in the
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_dma.c between commit 14c5cec5d0cd ("drm/i915:
initialize gt_lock early with other spin locks") from the drm-intel-fixes
tree and commit 907b28c56ea4 ("drm/i915: Colocate all GT access routines
in the
Hello,
On Thu, Jul 25, 2013 at 07:15:11PM -0400, Santosh Shilimkar wrote:
> Sorry if I wasn't clear before, but I need help to at least have new
> memblock API support since I am not familiar with memblock code.
> I could help in adaptation to the new API for ARM arch and
> core kernel code.
>
>
Hello,
On Fri, Jul 26, 2013 at 10:13:25AM +0800, Lai Jiangshan wrote:
> > Hmmm... if I'm not confused, now the cpu pools just behave like a
> > normal unbound pool when the cpu goes down,
>
> cpu pools are always referenced, they don't behave like unbound pool.
Yeah sure, they don't get destroye
Hi Frederic,
On 07/25/2013 07:00 PM, Frederic Weisbecker wrote:
> On Thu, Jul 25, 2013 at 02:33:02PM +0530, Preeti U Murthy wrote:
>> In the current design of timer offload framework, the broadcast cpu should
>> *not* go into tickless idle so as to avoid missed wakeups on CPUs in deep
>> idle sta
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/i915/i915_dma.c between commit 7dcd2677ea91 ("drm/i915:
fix long-standing SNB regression in power consumption after resume v2")
from Linus' tree and commit 59cdb63d529c ("drm/i915: kill
dev_priv->rps.lock") from th
On 2013-07-25 20:25, Konrad Rzeszutek Wilk wrote:
On Thu, Jul 25, 2013 at 02:52:00PM +0800, Zhenzhong Duan wrote:
On 2013-07-24 21:46, Konrad Rzeszutek Wilk wrote:
On Wed, Jul 24, 2013 at 11:08:10AM +0800, Zhenzhong Duan wrote:
xen_initdom_restore_msi_irqs trigger a hypercall to restore addr/
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
>> Can I get back on this topic. When USB and ethernet was working for me
>> as stated above, I was not doing tftpboot. When I use tftpboot the
>> images are obtained from the tftp server, but after kernel has started
>> there is nothing in /sys/
> From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com]
> Sent: Thursday, July 25, 2013 8:04 PM
>
> CC-ing some of the tboot maintainers.
> > As what I've said, it's up to the others to determine if the patch is OK.
> > I just need to make my concerns visible in the community. :-)
>
> If I
Hi Arend,
On 07/25/2013 08:06 AM, Arend van Spriel wrote:
> On 07/18/2013 02:42 PM, Roger Quadros wrote:
>> On 07/18/2013 03:38 PM, Arend van Spriel wrote:
>>> On 07/18/2013 01:30 PM, Roger Quadros wrote:
On 07/18/2013 02:24 PM, Arend van Spriel wrote:
> On 07/18/2013 01:18 PM, Roger Quad
On Thu, Jul 25, 2013 at 04:23:39PM +0800, zwu.ker...@gmail.com wrote:
> From: Zhi Yong Wu
>
> It can take a long time to run log recovery operation because it is
> single threaded and is bound by read latency. We can find that it took
> most of the time to wait for the read IO to occur, so if o
On Thu, 2013-07-25 at 08:50 +0200, rydb...@euromail.se wrote:
> Hi Ben,
>
> > 3.2.49-rc1 review patch. If anyone has any objections, please let me know.
>
> Because the bcm5974 patch is unsuitable for pre-3.7 kernels, this one
> is unsuitable as well; it renders the trackpad unusable. Without th
Hi Frederic,
On 07/25/2013 07:00 PM, Frederic Weisbecker wrote:
> On Thu, Jul 25, 2013 at 02:33:02PM +0530, Preeti U Murthy wrote:
>> In the current design of timer offload framework, the broadcast cpu should
>> *not* go into tickless idle so as to avoid missed wakeups on CPUs in deep
>> idle sta
On Wed, Jul 24, 2013 at 10:43:44AM +0200, Guennadi Liakhovetski wrote:
> Hi Morimoto-san
>
> On Tue, 23 Jul 2013, Kuninori Morimoto wrote:
>
> > sh_desc->hw.tcr is controlling real data size,
> > and, register TCR is controlling data transfer count
> > which was xmit_shifted value of hw.tcr.
> >
fix building warning and correct the binding doc
Signed-off-by: Robin Gong
---
.../devicetree/bindings/regulator/pfuze100.txt |2 ++
drivers/regulator/pfuze100-regulator.c |2 +-
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/devicetree/bindi
From: Wei Yongjun
A spin lock is taken here so we should use GFP_ATOMIC.
Signed-off-by: Wei Yongjun
---
drivers/staging/gdm724x/gdm_mux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gdm724x/gdm_mux.c
b/drivers/staging/gdm724x/gdm_mux.c
index f570bc0..7b
On Thu, Jul 25 2013, Nicholas A. Bellinger wrote:
> On Thu, 2013-07-25 at 12:16 +0200, Alexander Gordeev wrote:
> > On Mon, Jul 22, 2013 at 02:10:36PM -0700, Nicholas A. Bellinger wrote:
> > > Np. FYI, you'll want to use the latest commit e7827b351 HEAD from
> > > target-pending/scsi-mq, which now
On 07/25/2013 11:31 PM, Tejun Heo wrote:
> Hello, Lai.
>
> On Thu, Jul 25, 2013 at 06:52:02PM +0800, Lai Jiangshan wrote:
>> The unbound pools and their workers can be destroyed/cleared
>> when their refcnt become zero. But the cpu pool can't be destroyed
>> due to they are always referenced, thei
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Thursday, July 25, 2013 1:52 PM
>
> On Thu, Jul 25, 2013 at 07:46:58PM +, Paul Zimmerman wrote:
> > > diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> > > index 607bef8..50c833f 100644
> > > --- a/drivers/usb/dwc3/core.c
> > >
On Thu, Jul 25, 2013 at 09:38:44PM +0800, zwu.ker...@gmail.com wrote:
> From: Zhi Yong Wu
>
> When running the compilebench, one assertion failure was found.
> This related line of code was introduced by commit 5f6bed76c0.
>
> commit 5f6bed76c0c85cb4d04885a5de00b629deee550b
> Author: Dave Chin
The change:
commit f4e0c30c191f87851c4a53454abb55ee276f4a7e
Author: Al Viro
Date: Tue Jun 11 08:34:36 2013 +0400
allow the temp files created by open() to be linked to
O_TMPFILE | O_CREAT => linkat() with AT_SYMLINK_FOLLOW and /proc/self/fd/
as oldpath (i.e. flink()) will create a
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, July 26, 2013 5:29 AM
>
> On Tuesday, July 23, 2013 04:09:43 PM Lv Zheng wrote:
> > This patch adds reference couting for ACPI operation region handlers to fix
> > races caused by the ACPICA address space callback invocations.
> >
> >
The systemtap team announces release 2.3, "jbnq fdhvjjry"!
improved pass-2 error messages, runtime preprocessor conditionals,
global module variable visibility, internal improvements,
colorized error messages, uprobe pre-filtering, re-written
regular expression support
= Where to get
On 07/26/2013 07:15 AM, Dave Hansen wrote:
> I've got a relatively new system that doesn't seem to be able to hotplug
> SATA disks. I see the same behavior on 3.10, 3.11-rc2, and Ubuntu's
> 3.8.0-25-generic. The disks are detected right away on reboots, but
> even after poking the /sys/class/scsi
> From: Corey Minyard [mailto:tcminy...@gmail.com]
> Sent: Friday, July 26, 2013 8:48 AM
>
> On 07/25/2013 07:16 PM, Zheng, Lv wrote:
> >>
> >> If I understand this correctly, the problem would be if:
> >>
> >> rem_time = wait_for_completion_timeout(&tx_msg->tx_complete,
> >>
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, July 26, 2013 6:26 AM
>
> On Tuesday, July 23, 2013 04:10:06 PM Lv Zheng wrote:
> > This is a trivial patch:
> > 1. Deletes a member of the acpi_ipmi_device - smi_data which is not
> >actually used.
> > 2. Updates a member of the
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Friday, July 26, 2013 6:23 AM
>
> On Tuesday, July 23, 2013 04:09:54 PM Lv Zheng wrote:
> > This patch adds reference counting for ACPI IPMI transfers to tune the
> > locking
Hi Neil,
> Sorry I'm a bit late to the thread, I've ben swamped. Has someone
> tested this with kexec/kdump? Thats why the origional patch was
> created, because when kexec loads the kernel at a different physical
> address, the relocations messed with the module crc's, and modules
> couldn't l
Hi all,
Today's linux-next merge of the ia64 tree got conflicts in
arch/ia64/configs/generic_defconfig,
arch/ia64/configs/gensparse_defconfig, arch/ia64/configs/tiger_defconfig
and arch/ia64/configs/xen_domu_defconfig between commit eeaa9b427947
("PCI: hotplug: Convert to be builtin only, not modu
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, July 26, 2013 5:59 AM
>
> On Tuesday, July 23, 2013 04:09:26 PM Lv Zheng wrote:
> > This patch uses reference counting to fix the race caused by the
> > unprotected ACPI IPMI user.
> >
> > As the acpi_ipmi_device->user_interface check
On 07/26/2013 06:05 AM, Ingo Molnar wrote:
> * Chen Gang wrote:
>
>> On 07/23/2013 05:36 PM, Ingo Molnar wrote:
>>>
>>> (the crazies can keep a separate patch to remove even more of BUG() to win
>>> a K or two.)
>>>
>>
>> Excuse me, my English is not quite well, I do not quite understand your
>>
In the other mail thread, the related maintainer for s390 said:
"s390 will have GENERIC_HARDIRQS soon (very likely next merge window)"
For efficiency reason, I should stop trying this issue any more.
I found this issue by building s390 with allmodconfig, but s390 will be OK
for this issue
On 07/25/2013 04:17 PM, Jesse Barnes wrote:
> Well, it's ok if the boot loader writes to this memory, the worst
> that'll happen is you'll see garbage on the screen. If the boot loader
> tries to do MMIO mapping on top it'll get into trouble... but why would
> it do that?
>
> Jesse
Much worse: i
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, July 26, 2013 4:27 AM
>
> On Tuesday, July 23, 2013 04:09:43 PM Lv Zheng wrote:
> > This patch adds reference couting for ACPI operation region handlers
> > to fix races caused by the ACPICA address space callback invocations.
> >
>
On 07/25/2013 05:31 PM, Linus Torvalds wrote:
> On Thu, Jul 25, 2013 at 3:42 PM, H. Peter Anvin wrote:
>> So the bootloader is just as likely to step on things... what happens
>> when/if it does?
>
> This isn't a new problem. We've had this "firmware tables don't show
> all devices" issue before
On 07/25/2013 07:16 PM, Zheng, Lv wrote:
If I understand this correctly, the problem would be if:
rem_time = wait_for_completion_timeout(&tx_msg->tx_complete,
IPMI_TIMEOUT);
returns on a timeout, then checks msg_done and races with something setting
ms
Hi Linus,
The following changes since commit 3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b:
Linux 3.11-rc2 (2013-07-21 12:05:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to 515c0
On 07/25/2013 01:16 PM, Rob Herring wrote:
> On Thu, Jul 25, 2013 at 2:31 PM, Jason Cooper wrote:
>> On Thu, Jul 25, 2013 at 02:11:31PM -0500, Rob Herring wrote:
>>> On Thu, Jul 25, 2013 at 11:09 AM, Olof Johansson wrote:
>>
One problem that needs to be solved is obviously how a binding
The following changes since commit 30bc9b53878a9921b02e3b5bc4283ac1c6de102a:
md/raid1: fix bio handling problems in process_checks() (2013-07-18 14:18:04
+1000)
are available in the git repository at:
git://neil.brown.name/md tags/md/3.11-fixes
for you to fetch changes up to f94c0b6658c7ed
On 07/25/2013 02:53 PM, Ben Hutchings wrote:
> On Thu, Jul 25, 2013 at 04:32:28PM -0400, Jason Cooper wrote:
> [...]
>> One of the things I've been trying to square up in my head is how to
>> retain the history of the binding when moving to the new tree. My
>> current idea was to clone the kernel
On Thu, 25 Jul 2013 19:10:50 -0400 "Justin Piszcz"
wrote:
>
>
> -Original Message-
> From: NeilBrown [mailto:ne...@suse.de]
> Sent: Sunday, July 21, 2013 7:03 PM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
> Subject: Re: 3.10.1: echo repair > sync
On Thu, Jul 25, 2013 at 3:42 PM, H. Peter Anvin wrote:
> So the bootloader is just as likely to step on things... what happens when/if
> it does?
This isn't a new problem. We've had this "firmware tables don't show
all devices" issue before.
The only odd thing about this one is how the quirk in
On Thu, Jul 25, 2013 at 7:18 PM, Russell King - ARM Linux
wrote:
> On Thu, Jul 25, 2013 at 03:31:35PM -0400, Jason Cooper wrote:
>> On Thu, Jul 25, 2013 at 02:11:31PM -0500, Rob Herring wrote:
>> > On Thu, Jul 25, 2013 at 11:09 AM, Olof Johansson wrote:
>>
>> > > One problem that needs to be solv
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Friday, July 26, 2013 3:33 AM
>
> On Thursday, July 25, 2013 01:12:38 PM Corey Minyard wrote:
> > On 07/25/2013 07:06 AM, Rafael J. Wysocki wrote:
> > > On Thursday, July 25,
1 - 100 of 729 matches
Mail list logo
