Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
Signed-off-by: Alexey Brodkin
Cc: Andy Shevchenko
Cc: Francois Romieu
Cc: Joe Perches
Cc: Vineet Gupta
Cc: Mischa Jonker
Cc: Arnd Bergmann
Cc:
Ping!
FYI, I rebased the perf/cleanup branch on top of current acme/perf/core.
Thanks,
Namhyung
2013-06-04 PM 2:20, Namhyung Kim wrote:
Hello,
This patchset is a resend version of previous work and basis of
upcoming perf ftrace patchset. Although I saw no issue on this series
when I posted
On 23 June 2013 04:38, Heiko Stübner wrote:
> Commit 5070158804b5 (cpufreq: rename index as driver_data in
> cpufreq_frequency_table) renamed the index field to driver_data.
>
> But it seems some uses in the s3c2416 driver were forgotten.
>
> So convert the last index users to read driver_data.
>
Hi Rafael,
This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
sequence". It contains changes specific to cpufreq core and ARM drivers.
I have left changes to non-ARM cpufreq drivers from this pull request. See if
you can take them for 3.11.
The following changes since
Hi Mike,
Today's linux-next merge of the clk tree got a conflict in
drivers/clk/samsung/clk-exynos4.c between commit 6082f908b060 ("clk:
exynos4: Staticize local symbols") from the samsung tree and commit
82ba93b27cf5 ("clk: exynos4: Fix clock aliases for cpufreq related
clocks") from the clk
Hi,
On Tuesday 18 June 2013 03:17 PM, Felipe Balbi wrote:
Hi,
On Thu, Jun 13, 2013 at 02:13:57PM +0530, Kishon Vijay Abraham I wrote:
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on/get_sync and
power_off/put_sync to
Hi,
On Fri, 21 Jun 2013 10:24:44 -0500 Suman Anna wrote:
>
> On 06/21/2013 02:36 AM, Arnd Bergmann wrote:
> > On Friday 21 June 2013, Tony Lindgren wrote:
> >>> I wonder if this mess is caused by the fact that I did the revert
> >>> instead of rebuilding our for-next and dropping the merge in
Hi,
On Saturday 22 June 2013 06:42 PM, Laxman Dewangan wrote:
On Friday 21 June 2013 07:30 PM, Kishon Vijay Abraham I wrote:
On Friday 21 June 2013 06:55 PM, Laxman Dewangan wrote:
On Thursday 20 June 2013 08:56 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 20 June 2013 08:14 PM, Laxman
On Mon, 2013-06-24 at 13:52 +1000, David Gibson wrote:
> On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
> > On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > > On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex Williamson wrote:
> > > > On Thu, 2013-06-20 at 18:48 +1000,
On Friday 21 June 2013 11:43 PM, Mike Turquette wrote:
> Quoting Ambresh K (2013-06-17 01:39:44)
>> From: Ambresh K
>>
>> clk_ops's .get_parent member data return's signed value.
>>
>> Signed-off-by: Ambresh K
>
> Unsurprisingly I get the following errors when building
> multi_v7_defconfig:
>
On Mon, Jun 24, 2013 at 11:49:49AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2013-06-21 at 09:54 -0700, Guenter Roeck wrote:
>
> > > v2: Ensure that PCI bus fixup code has been executed before calling
> > > device setup code.
> > >
> > Hi Ben,
> >
> > any comments/feedback on this
On Sun, Jun 23, 2013 at 5:40 PM, Rafael J. Wysocki wrote:
> On Sunday, June 23, 2013 04:04:52 PM Yinghai Lu wrote:
>> On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
...
>> > Ah, I overlooked the fact that each dock station is on its own
>> > dependent_list
>> > and can also be on
On 06/23/2013 07:56 PM, Ren Qiaowei wrote:
>>
> Well, I guess that I can use iomem related interface to fix these
> warnings caused by sparse.
>
And you SHOULD. Passing around pointers to I/O space without even
annotating them isn't really very clean.
-hpa
--
To unsubscribe from this
On 24/06/2013 04:44, David Miller wrote:
From: Eliezer Tamir
Date: Wed, 19 Jun 2013 13:04:21 +0300
One question: do we need in sock_poll() to test that sock->sk is not null?
(Thanks to Willem de Bruijn for pointing this out.)
We should not have to.
Please clean up various things in this
From: Guenter Roeck
Add gpio support for the on-board PLD found on some Kontron embedded modules.
Originally-From: Michael Brunner
Signed-off-by: Guenter Roeck
Signed-off-by: Kevin Strasser
Acked-by: Darren Hart
Reviewed-by: Linus Walleij
---
drivers/gpio/Kconfig | 12 +++
Add watchdog timer support for the on-board PLD found on some Kontron embedded
modules.
Originally-From: Michael Brunner
Signed-off-by: Kevin Strasser
Acked-by: Guenter Roeck
Acked-by: Darren Hart
---
drivers/watchdog/Kconfig | 11 +
drivers/watchdog/Makefile |1 +
Add i2c support for the on-board PLD found on some Kontron embedded
modules.
Originally-From: Michael Brunner
Signed-off-by: Kevin Strasser
Acked-by: Guenter Roeck
Acked-by: Darren Hart
---
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile |1 +
Add core MFD driver for the on-board PLD found on some Kontron embedded
modules. The PLD device may provide functions like watchdog, GPIO, UART
and I2C bus.
The following modules are supported:
* COMe-bIP#
* COMe-bPC2 (ETXexpress-PC)
* COMe-bSC# (ETXexpress-SC T#)
Changes since v2:
-Change Michael's "Signed-off-by" to "Originally-From" in all patches
-Add "From: Guenter Roeck " to gpio patch
Guenter Roeck (1):
gpio: Kontron PLD gpio driver
Kevin Strasser (3):
mfd: Kontron PLD mfd driver
i2c: Kontron PLD i2c bus driver
watchdog: Kontron PLD
On Mon, 2013-06-24 at 13:54 +1000, David Gibson wrote:
> > DDW means an API by which the guest can request the creation of
> > additional iommus for a given device (typically, in addition to the
> > default smallish 32-bit one using 4k pages, the guest can request
> > a larger window in 64-bit
On Fri, Jun 21, 2013 at 8:01 PM, Eduardo Valentin
wrote:
> On 20-06-2013 22:01, amit daniel kachhap wrote:
>> Hi Eduardo,
>>
>> On Thu, Jun 20, 2013 at 1:25 AM, Eduardo Valentin
>> wrote:
>>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
This patch adds some extra register bitfield
On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
> On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex Williamson wrote:
> > > On Thu, 2013-06-20 at 18:48 +1000, Alexey Kardashevskiy wrote:
> > > > On 06/20/2013 05:47 PM,
On Sun, Jun 23, 2013 at 09:28:13AM +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > I think the interface should not take the group fd, but the container
> > fd. Holding a reference to *that* would keep the necessary things
> > around. But more to
On 06/22/2013 02:25 AM, Tejun Heo wrote:
Hey,
On Fri, Jun 21, 2013 at 05:19:48PM +0800, Tang Chen wrote:
* As memblock allocator can relocate itself. There's no point in
avoiding setting NUMA node while parsing and registering NUMA
topology. Just parse and register NUMA info and later
On Mon, 24 Jun 2013, majianpeng wrote:
> Because in func queue_con_delay, it will call con->ops->get(con).
> So if we cancel the work successfully,we must call con->ops->put(con).
> Otherwise some resource can't free like 'struct ceph_mds_session'.
>
> Signed-off-by: Jianpeng Ma
Looks good,
On 06/23/2013 10:26 PM, Michael S. Tsirkin wrote:
> get user pages might fail partially in macvtap zero copy
> mode. To recover we need to put all pages that we got,
> but code used a wrong index resulting in double-free
> errors.
>
> Reported-by: Brad Hubbard
> Signed-off-by: Michael S. Tsirkin
On 06/23/2013 10:19 PM, Michael S. Tsirkin wrote:
> get user pages might fail partially in tun zero copy
> mode. To recover we need to put all pages that we got,
> but code used a wrong index resulting in double-free
> errors.
>
> Reported-by: Brad Hubbard
> Signed-off-by: Michael S. Tsirkin
>
On 06/20/2013 10:18 AM, Alex Shi wrote:
> Resend patchset for more convenient pick up.
> This patch set combine 'use runnable load in balance' serials and 'change
> 64bit variables to long type' serials. also collected Reviewed-bys, and
> Tested-bys.
>
> The only changed code is fixing load to
On Mon, Jun 24, 2013 at 12:44:59PM +1000, Dave Chinner wrote:
>
> Hence, at minimum, this should be a fallocate() operation, not a ext4
> specific ioctl as it is relatively trivial to implement on most
> extent based filesystems.
The fallocate() uses a units of bytes for the offset and length;
On 06/23/2013 04:36 PM, Joe Perches wrote:
On Sun, 2013-06-23 at 15:54 +0800, Qiaowei Ren wrote:
These logs come from tboot (Trusted Boot, an open source,
pre-kernel/VMM module that uses Intel TXT to perform a
measured and verified launch of an OS kernel/VMM.).
[]
diff --git
On Thu, Jun 20, 2013 at 10:00 PM, Geremy Condra wrote:
> With this change dm-verity errors will cause uevents to be
> sent to userspace, notifying it that an error has occurred
> and potentially triggering recovery actions.
>
> Signed-off-by: Geremy Condra
> ---
> Changelog since v1:
> - Removed
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/drm_prime.c between commit ebc0bad4a05a ("drm/prime:
Honor requested file flags when exporting a buffer") from Linus' tree and
commit ca793f75d91d ("drm: move pinning/unpinning to buffer attach") from
the drm
On Friday, June 21, 2013 11:15 PM, Arnd Bergmann wrote:
> On Friday 21 June 2013, Jason Cooper wrote:
> > On Fri, Jun 21, 2013 at 10:30:47AM +0200, Arnd Bergmann wrote:
> > > On Friday 21 June 2013, Thomas Petazzoni wrote:
> > > > I am by far not an expert on how to solve merge strategies and so
On Sun, Jun 23, 2013 at 08:32:32PM -0400, Eric Sandeen wrote:
> On Jun 23, 2013, at 12:01 PM, Andreas Dilger wrote:
>
> > On 2013-06-23, at 0:07, Namjae Jeon wrote:
> >
> >> From: Namjae Jeon
> >>
> >> This patch series introduces 2 new ioctls for ext4.
> >>
> >> Truncate_block_range ioctl
On Fri, Jun 21, 2013 at 11:24 PM, Mark Brown wrote:
> On Thu, Jun 20, 2013 at 03:31:07AM -0400, Chao Xie wrote:
>
> Looks pretty good, main thing here is that some of the functionality
> here appears to be reproducing standard code.
>
>> +static int pm800_set_voltage(struct regulator_dev *rdev,
On Sun, Jun 23, 2013 at 06:04:52PM +0200, Oleg Nesterov wrote:
> Could you please do the following:
>
> 1. # cd /sys/kernel/debug/tracing
> # echo 0 >> options/function-trace
> # echo preemptirqsoff >> current_tracer
dammit.
WARNING: at include/linux/list.h:385
On 2013-06-23, at 0:07, Namjae Jeon wrote:
> From: Namjae Jeon
> The EXT4_IOC_TRUNCATE_BLOCK_RANGE removes the data blocks lying
> between [start, "start + length") and updates the logical block numbers
> of data blocks starting from "start + length" block to last block of file.
> This will
Hi,
On 2013년 06월 22일 00:19, Mark Brown wrote:
> On Thu, Jun 20, 2013 at 04:03:26PM +0900, Jonghwa Lee wrote:
>> This patch adds new regulator driver to support max77693 chip's regulators.
>> max77693 has two linear voltage regulators and one current regulator which
>> can be controlled through
On Fri, 2013-06-21 at 09:54 -0700, Guenter Roeck wrote:
> > v2: Ensure that PCI bus fixup code has been executed before calling
> > device setup code.
> >
> Hi Ben,
>
> any comments/feedback on this approach ?
>
> It is much less invasive than before and should address your concerns.
And
From: Eliezer Tamir
Date: Wed, 19 Jun 2013 13:04:21 +0300
> One question: do we need in sock_poll() to test that sock->sk is not null?
> (Thanks to Willem de Bruijn for pointing this out.)
We should not have to.
Please clean up various things in this patch:
1) You have cases where you add
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get a few small
fixups for cyttsp, wacom and xpad
On Thu, Jun 20, 2013 at 8:51 PM, Jiri Slaby wrote:
> On 06/20/2013 02:28 PM, tingwei liu wrote:
>> Hi, dears:
>>
>> On Suse 11 sp2 3.0.13 kernel. After a few days, Nginx reply
>> packets with src ip 0.0.0.0 and dst ip 0.0.0.0。
>> Just like
From: Wedson Almeida Filho
Date: Fri, 14 Jun 2013 17:54:29 -0700
> Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
> even when consuming all the data because the last call to skb_seq_read (the
> one that returns 0 to indicate the end) fails to unmap the last fragment
Hi Al,
After merging the vfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from arch/powerpc/xmon/xmon.c:41:0:
arch/powerpc/include/asm/spu.h:245:43: error: 'struct coredump_params' declared
inside parameter list [-Werror]
int
Because in func queue_con_delay, it will call con->ops->get(con).
So if we cancel the work successfully,we must call con->ops->put(con).
Otherwise some resource can't free like 'struct ceph_mds_session'.
Signed-off-by: Jianpeng Ma
---
net/ceph/messenger.c | 3 ++-
1 file changed, 2
> Enable PSTORE in pseries_defconfig
Please add a "why" to your changelogs eg. "Now we have pstore support for
nvram on pseries, enable it in the default config"
"Why" you are changing something is more important than "what", since
you can always determine "what" is being changed, by looking at
On Fri, 2013-06-21 at 17:07 -0400, Eduardo Valentin wrote:
> To reduce thermal maintenance load on Rui, SoC specific patches would be
> applied by me now. Rui Zhang will pull in these changes from time to time (at
> rc's). Additionally I would be sending him pull request for every merge
> window
On Jun 23, 2013, at 12:01 PM, Andreas Dilger wrote:
> On 2013-06-23, at 0:07, Namjae Jeon wrote:
>
>> From: Namjae Jeon
>>
>> This patch series introduces 2 new ioctls for ext4.
>>
>> Truncate_block_range ioctl truncates blocks from source file.
>
> How is this different from
On Sunday, June 23, 2013 04:04:52 PM Yinghai Lu wrote:
> On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
> > On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
> >> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
> >> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
> >> >>
The aliasing doesn't matter for Linux because we map the high and low half the
same.
Henrique de Moraes Holschuh wrote:
>On Sun, 23 Jun 2013, H. Peter Anvin wrote:
>> On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
>> >
>> > And as far as I could find from Intel's not-that-complete
On Sun, Jun 23, 2013 at 06:04:52PM +0200, Oleg Nesterov wrote:
> > [11018.927809] [sched_delayed] sched: RT throttling activated
> > [11054.897670] BUG: soft lockup - CPU#2 stuck for 22s!
> > [trinity-child2:14482]
> > [11054.898503] Modules linked in: bridge stp snd_seq_dummy tun fuse hidp
On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
> >
> > And as far as I could find from Intel's not-that-complete public
> > "specification updates", we are applying the errata workaround to a few more
> > processors than strictly required,
On Sat, 22 Jun 2013 11:04:27 -1000 Linus Torvalds
wrote:
>
> So this is hopefully the last -rc in the series, and things have
> indeed be calming down finally, so assuming that trend continues,
> we're all good.
And you are all going to resist rebasing your trees (for no apparent
reason) this
On Fri, 2013-06-21 at 14:34 -0700, Arjan van de Ven wrote:
> On 6/21/2013 2:23 PM, Catalin Marinas wrote:
> >>
> >> oops sorry I misread your mail (lack of early coffee I suppose)
> >>
> >> I can see your point of having a thing for "did we ask for all the
> >> performance
> >> we could ask for"
On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
> On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
>> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
>> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
>> >> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
>> >>> From:
On Sun, Jun 23, 2013 at 1:38 PM, H. Peter Anvin wrote:
> On 06/23/2013 01:30 PM, Dave Airlie wrote:
> Why do you care about performance when PAT is disabled?
>>
>> breaking old boxes just because, is just going to get reverted when I
>> get the first regression report that you broke old
Am Samstag, 15. Juni 2013, 16:23:24 schrieb Lars-Peter Clausen:
> The I2C client driver is not supposed to modify the client's driver
> pointer, this is handled by the I2C core.
>
> Signed-off-by: Lars-Peter Clausen
> ---
Nice catch.
Staged here:
This patch should fix the following bug reported by kbuild test robot.
fs/f2fs/recovery.c:233:33: sparse: incorrect type in assignment
(different base types)
parse warnings: (new ones prefixed by >>)
>> fs/f2fs/recovery.c:233:33: sparse: incorrect type in assignment (different
>> base types)
On 13-06-23 05:51 PM, Pavel Machek wrote:
> On Sun 2013-06-23 17:27:52, Mark Lord wrote:
>
>> For all existing drives out there, that's a 512 byte unit.
>
> I guessed so. (It would be good to actually document it, as well as
> documenting exactly why it is dangerous. Is it okay to send patches?)
On 6/23/13 3:09 AM, Ingo Molnar wrote:
If an IO driver is implemented properly then it will batch up requests for
the controller, and gets IRQ-notified on a (sub-)batch of buffers
completed.
If there's any spinning done then it should be NAPI-alike polling: a
single "is stuff completed" polling
On Fri, Jun 14, 2013 at 06:04:34PM -0700, Christian Kujau wrote:
> I just stumbled across another[0] issue when scripts/setlocalversion
> operates on a write-protected source tree. Back then[0] the source tree
> was on an read-only NFS share, so "test -w" was introduced before "git
>
On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
>
> And as far as I could find from Intel's not-that-complete public
> "specification updates", we are applying the errata workaround to a few more
> processors than strictly required, but since I have no idea how to write a
> test case,
On Fri, Jun 21, 2013 at 04:20:40PM +0200, Stephane Eranian wrote:
> This patch series extends perf_events with the ability to sample
> physical data addresses. This is useful with the memory access
> sampling mode added just recently. In particular, it helps
> disambiguate data addresses between
On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> On 06/23/2013 12:29 PM, Henrique de Moraes Holschuh wrote:
> > On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> >> Why do you care about performance when PAT is disabled?
> >
> > It will regress already slow boxes. We blacklist a LOT of P4s, PMs, etc and
On Sat, Jun 22, 2013 at 11:17:20PM -0400, Greg Price wrote:
> For example, in an application with an expensive function
> implemented with deeply nested recursive calls, the default
> call-graph presentation is dominated by the different callchains
> within that function. By treating the function
On Sun 2013-06-23 17:27:52, Mark Lord wrote:
> On 13-06-23 03:00 PM, Pavel Machek wrote:
> >
> > Thanks for the hint. (Insert rant about hdparm documentation
> > explaining that it is bad idea, but not telling me _why_ is it bad
> > idea. Can I expect cache consistency issues after that, or is it
On Sunday, June 23, 2013 04:34:17 AM Joe Perches wrote:
> On Sun, 2013-06-23 at 13:36 +0200, Rafael J. Wysocki wrote:
> > Please keep the existing format as is literally and append any
> > new information to the end of the line.
>
> Hi Shuah.
>
> Perhaps the better long-term approach would be to
On Sunday, June 23, 2013 11:57:46 PM Jiang Liu wrote:
> On 06/23/2013 03:59 AM, Rafael J. Wysocki wrote:
> > On Saturday, June 22, 2013 10:47:24 AM Jiang Liu wrote:
> >> On 06/22/2013 08:13 AM, Rafael J. Wysocki wrote:
> >>> On Saturday, June 22, 2013 12:54:21 AM Jiang Liu wrote:
> On
On Sunday, June 23, 2013 11:57:46 PM Jiang Liu wrote:
> On 06/23/2013 03:59 AM, Rafael J. Wysocki wrote:
> > On Saturday, June 22, 2013 10:47:24 AM Jiang Liu wrote:
> >> On 06/22/2013 08:13 AM, Rafael J. Wysocki wrote:
> >>> On Saturday, June 22, 2013 12:54:21 AM Jiang Liu wrote:
> On
On 13-06-23 03:00 PM, Pavel Machek wrote:
>
> Thanks for the hint. (Insert rant about hdparm documentation
> explaining that it is bad idea, but not telling me _why_ is it bad
> idea. Can I expect cache consistency issues after that, or is it just
> simple "you are writing to the disk without any
On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
> >> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
> >>> From: Rafael J. Wysocki
> >>>
> >>> The interactions between the ACPI
Hi Gabriel,
sorry for the late feedback.
Dne 10.6.2013 17:28, Gabriel de Perthuis napsal(a):
> Use RCS_FIND_IGNORE in more places.
Can you split it into two parts - one adding the missing RCS_FIND_IGNORE
to some find invocations, and other adding the -xdev option? While the
first change is
On Mon, Jun 24, 2013 at 6:58 AM, H. Peter Anvin wrote:
> On 06/23/2013 01:54 PM, Dave Airlie wrote:
breaking old boxes just because, is just going to get reverted when I
get the first regression report that you broke old boxes.
>>>
>>> Not "just because", but *if* the choice is
Hi Michal,
On 08/06/13 01:58 PM, Graeme Smecher wrote:
Hi all,
On 08/06/13 09:52 AM, Graeme Smecher wrote:
Other architectures don't do it, and it conflicts with the extern'd
definition
in include/linux/kgdb.h.
Signed-off-by: Graeme Smecher
CC: Michal Simek
CC:linux-kernel@vger.kernel.org
On Sunday, June 23, 2013 11:50:15 PM Alexander E. Patrakov wrote:
> 2013/6/23 Rafael J. Wysocki :
> > Alexander, I've modified patch [3/3] a bit since you have tested it.
> > The modifications shouldn't affect the behavior, but if you could re-test
> > it,
> > that would be great.
>
> Retested,
On 06/23/2013 01:54 PM, Dave Airlie wrote:
>>> breaking old boxes just because, is just going to get reverted when I
>>> get the first regression report that you broke old boxes.
>>>
>>
>> Not "just because", but *if* the choice is between breaking old boxes
>> and breaking new boxes I'll take the
>> breaking old boxes just because, is just going to get reverted when I
>> get the first regression report that you broke old boxes.
>>
>
> Not "just because", but *if* the choice is between breaking old boxes
> and breaking new boxes I'll take the latter.
>
But Linus won't so your choice
On 06/23/2013 01:30 PM, Dave Airlie wrote:
Why do you care about performance when PAT is disabled?
>
> breaking old boxes just because, is just going to get reverted when I
> get the first regression report that you broke old boxes.
>
Not "just because", but *if* the choice is between
>>> Why do you care about performance when PAT is disabled?
breaking old boxes just because, is just going to get reverted when I
get the first regression report that you broke old boxes.
Andy Lutomirski just submitted a bunch of patches to clean up the DRM
usage of mtrrs, they are in drm-next,
On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
> On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
>> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki
>>>
>>> The interactions between the ACPI dock driver and the ACPI-based PCI
>>> hotplug (acpiphp) are
On Sat, 2013-06-22 at 03:57 -0400, Peter Hurley wrote:
> On 06/21/2013 07:51 PM, Tim Chen wrote:
> > Introduce in this patch optimistic spinning for writer lock
> > acquisition in read write semaphore. The logic is
> > similar to the optimistic spinning in mutex but without
> > the MCS lock
On 06/23/2013 12:29 PM, Henrique de Moraes Holschuh wrote:
> On Sun, 23 Jun 2013, H. Peter Anvin wrote:
>> Why do you care about performance when PAT is disabled?
>
> It will regress already slow boxes. We blacklist a LOT of P4s, PMs, etc and
> nobody ever took the pain to track down which ones
> "Joseph" == Joseph CHANG writes:
Joseph> DM9620 is an USB2.0 network adapter rather than DM9601 USB1.1. This
Joseph> driver processed the RX data 4 bytes header, TX data 2 bytes header,
Joseph> make the control bit exactly right in PHY write function, and optional
Joseph> IFF_ALLMUTLI
On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> The interactions between the ACPI dock driver and the ACPI-based PCI
>> hotplug (acpiphp) are currently problematic because of ordering
>> issues during
hw start may fail therefore the reset flow has
to check for the return value
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/init.c| 7 ++-
drivers/misc/mei/mei_dev.h | 4 ++--
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/mei/init.c
On Sun, Jun 23, 2013 at 2:59 AM, Rafael J. Wysocki wrote:
> On Saturday, June 22, 2013 05:22:20 PM Yinghai Lu wrote:
>> On Sat, Jun 22, 2013 at 2:25 PM, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > To resolve that deadlock use the observation that
>> >
On Sun, Jun 23, 2013 at 9:29 PM, Joe Perches wrote:
>> While we're at it, paddr is phys_addr_t (which can be 32-bit or 64-bit),
>> so it should be cast to unsigned long long (instead of unsigned long),
>> and printed using %llx (instead of %lx).
>
> Sounds good to me, except using %pa instead is
On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> Why do you care about performance when PAT is disabled?
It will regress already slow boxes. We blacklist a LOT of P4s, PMs, etc and
nobody ever took the pain to track down which ones of those actually have
PAT+MTRR aliasing bugs.
These boxes have
printk supports using %pa for phys_addr_t and
%zx for size_t so use those instead of %lx and
casts to unsigned long.
Other miscellaneous changes around this:
Always use 0x%zx for size instead of one use of decimal.
Coalesce format and align arguments.
Signed-off-by: Joe Perches
---
> While
On Mon, 2013-06-24 at 00:25 +0530, Srivatsa S. Bhat wrote:
> On 06/23/2013 11:47 PM, Greg Kroah-Hartman wrote:
> > On Sun, Jun 23, 2013 at 07:13:33PM +0530, Srivatsa S. Bhat wrote:
[]
> >> diff --git a/drivers/staging/octeon/ethernet-rx.c
> >> b/drivers/staging/octeon/ethernet-rx.c
[]
> Honestly,
On Sun, Jun 23, 2013 at 7:43 PM, Joe Perches wrote:
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -807,20 +807,19 @@ int iommu_map(struct iommu_domain *domain, unsigned
> long iova,
> * size of the smallest page supported by the hardware
> */
> if
On 06/23/2013 08:38 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 23-06-2013 17:39, Srivatsa S. Bhat wrote:
>
>> Now that we have all the pieces of the CPU hotplug debug infrastructure
>> in place, expose the feature by growing a new Kconfig option,
>> CONFIG_DEBUG_HOTPLUG_CPU.
>
>> Cc: Andrew
Hi!
> > ...Ok, lets try with dd.
> >
> > root@amd:~# dd if=/dev/sda4 of=/dev/zero bs=1 skip=8958947328
> > dd: reading `/dev/sda4': Input/output error
> > 0+0 records in
> > 0+0 records out
> > 0 bytes (0 B) copied, 5.05805 s, 0.0 kB/s
>
> I once noticed a similar problem. The trouble is that
On 06/23/2013 11:20 PM, Matt Turner wrote:
> On Sun, Jun 23, 2013 at 6:45 AM, Srivatsa S. Bhat
> wrote:
>> Once stop_machine() is gone from the CPU offline path, we won't be able
>> to depend on disabling preemption to prevent CPUs from going offline
>> from under us.
>>
>> Use the
On 06/23/2013 11:47 PM, Greg Kroah-Hartman wrote:
> On Sun, Jun 23, 2013 at 07:13:33PM +0530, Srivatsa S. Bhat wrote:
>> Once stop_machine() is gone from the CPU offline path, we won't be able
>> to depend on disabling preemption to prevent CPUs from going offline
>> from under us.
>>
>> Use the
On Wed, Jun 19, 2013 at 12:15:53PM -0700, Joe Perches wrote:
> Don't emit OOM warnings when k.alloc calls fail when
> there there is a v.alloc immediately afterwards.
>
> Signed-off-by: Joe Perches
For fs/ext4/super.c:
Acked-by: "Theodore Ts'o"
- Ted
On Sun, Jun 23, 2013 at 12:09 AM, Ingo Molnar wrote:
>
> The spinning approach you add has the disadvantage of actively wasting CPU
> time, which could be used to run other tasks. In general it's much better
> to make sure the completion IRQs are rate-limited and just schedule. This
> (combined
On Sun, Jun 23, 2013 at 07:13:33PM +0530, Srivatsa S. Bhat wrote:
> Once stop_machine() is gone from the CPU offline path, we won't be able
> to depend on disabling preemption to prevent CPUs from going offline
> from under us.
>
> Use the get/put_online_cpus_atomic() APIs to prevent CPUs from
> Good question! I tried disabling CPA self-test and the BUG does not
> show up for 1 boots. So this should be the root cause.
>
The test is very different now than what I wrote originally, but I would
generally expect any bug to be in change_page_attr(), not be in the
self test.
> > > [
On Sun, Jun 23, 2013 at 6:45 AM, Srivatsa S. Bhat
wrote:
> Once stop_machine() is gone from the CPU offline path, we won't be able
> to depend on disabling preemption to prevent CPUs from going offline
> from under us.
>
> Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
>
1 - 100 of 490 matches
Mail list logo
