Resuming a switcheroo'd HDA controller hangs since the completion
is one-shot (thus works the first time). Fix by using completions
that explictly need rearming, so remain fired before.
Signed-off-by: Daniel J Blueman
---
sound/pci/hda/hda_intel.c |4 ++--
1 file changed, 2 insertions(+), 2
On Tue, 2012-12-18 at 02:48 +0100, Rafael J. Wysocki wrote:
> On Monday, December 17, 2012 05:08:17 PM Toshi Kani wrote:
> > On Thu, 2012-12-13 at 23:17 +0100, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> >
> > (snip)
> >
> > > struct acpi_device_ops {
> > > Index:
On 12/18/2012 01:40 AM, stef...@seibold.net wrote:
> From: Stefani Seibold
>
> This patch adds support for 32 bit VDSO.
>
> For 32 bit programs running on a 32 bit kernel, the same mechanism is
> used as for 64 bit programs running on a 64 bit kernel.
>
> For 32 bit programs running under a 64
At Tue, 18 Dec 2012 23:59:33 +0800,
Daniel J Blueman wrote:
>
> Resuming a switcheroo'd HDA controller hangs since the completion
> is one-shot (thus works the first time). Fix by using completions
> that explictly need rearming, so remain fired before.
>
> Signed-off-by: Daniel J Blueman
Since e303297 (mm: extended batches for generic mmu_gather) we are batching
pages to be freed until either tlb_next_batch cannot allocate a new batch or we
are done.
This works just fine most of the time but we can get in troubles with
non-preemptible kernel (CONFIG_PREEMPT_NONE or
On 05/12/12 18:39, Al Viro wrote:
> On Wed, Dec 05, 2012 at 05:11:32PM +, Al Viro wrote:
>> On Wed, Dec 05, 2012 at 04:08:18PM +, James Hogan wrote:
>>
>>> other work not included:
>>> * switch to generic kernel_{thread,execve} (will be posted separately to
>>> aid review)
>>
>>> other
On Tue, 18 Dec 2012, Venu Byravarasu wrote:
> As pointer to PHY structure can be stored in struct usb_hcd
> making use of it, to call PHY APIs.
>
> Call to usb_phy_shutdown() is moved up in tegra_ehci_remove(),
> so that to avoid dereferencing of hcd after its freed up.
>
> Signed-off-by: Venu
On Tue, Dec 18, 2012 at 04:51:28PM +0100, Paolo Bonzini wrote:
> Il 18/12/2012 16:03, Michael S. Tsirkin ha scritto:
> > On Tue, Dec 18, 2012 at 03:08:08PM +0100, Paolo Bonzini wrote:
> >> Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
> -static int virtscsi_queuecommand(struct Scsi_Host
On 12/14/2012 11:33 PM, Oleg Nesterov wrote:
> On 12/13, Srivatsa S. Bhat wrote:
>>
>> On 12/13/2012 09:47 PM, Oleg Nesterov wrote:
>>> On 12/13, Srivatsa S. Bhat wrote:
On 12/13/2012 12:42 AM, Srivatsa S. Bhat wrote:
>
> Even I don't spot anything wrong with it. But I'll give it
Il 18/12/2012 16:03, Michael S. Tsirkin ha scritto:
> On Tue, Dec 18, 2012 at 03:08:08PM +0100, Paolo Bonzini wrote:
>> Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
-static int virtscsi_queuecommand(struct Scsi_Host *sh, struct scsi_cmnd
*sc)
+static int
On Tue, Dec 18, 2012 at 5:36 AM, Christian König
wrote:
> On 17.12.2012 22:31, Paul Bolle wrote:
>>
>> On an (outdated) laptop the radeon driver (almost always) prints, during
>> the first resume of each session:
>> [drm] crtc 1 is connected to a TV
>>
>> This message is a bit puzzling as,
On Mon, Dec 17, 2012 at 03:38:58PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Show group members' overhead also when showing the leader's if event
> group is enabled. Use macro for defining hpp functions which looks
> almost identical.
SNIP
> -
> -static int
> Not only inform firmware.
> Hotplug notify callback will invoke acpi_bus_add -> ... ->
> implicitly invoke drv->ops.add method to add the hotadded memory
> device.
> >>>
> >>> Gotcha.
> >>
> >> ? So it will lose the notification and no way to add the new memory
> >> device
648bb56d07 ("cgroup: lock cgroup_mutex in cgroup_init_subsys()") made
cgroup_init_subsys() grab cgroup_mutex before invoking ->css_alloc()
for the root css. Because memcg registers hotcpu notifier from
->css_alloc() for the root css, this introduced circular locking
dependency between
On 12/17/2012 01:12 PM, Johannes Weiner wrote:
> A swappiness of 0 has a slightly different meaning for global reclaim
> (may swap if file cache really low) and memory cgroup reclaim (never
> swap, ever).
>
> In addition, global reclaim at highest priority will scan all LRU
> lists equal to
On Fri, Dec 14, 2012 at 1:22 PM, Peter Hurley wrote:
> I wasn't sure if this is something to squeeze into 3.8, so don't yell
> if not. At least Sasha can apply this and re-test against trinity.
>
> Changes in v2:
>
> - Please review "tty: Don't flush buffer when closing ldisc".
> This patch
On Mon, Dec 17, 2012 at 03:38:57PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
SNIP
> +static int hist_entry__sort_on_period(struct hist_entry *a,
> + struct hist_entry *b)
> +{
> + int ret;
> + int i, nr_members;
> + struct perf_evsel *evsel;
>
On Mon, Dec 17, 2012 at 03:38:54PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Use readn instead of read and check return value of do_write.
>
> Suggested-by: Arnaldo Carvalho de Melo
> Cc: Jiri Olsa
Acked-by: Jiri Olsa
--
To unsubscribe from this list: send the line "unsubscribe
Adding base address information required for enabling
USB 3.0 DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
This patch-set enables the samsung-usbphy driver on exynos5250,
which enables the support for USB2 type and USB3 type phys.
The corresponding phy driver patches are available at:
1) https://lkml.org/lkml/2012/12/18/201
2)
Adding usbphy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 22 ++
arch/arm/mach-exynos/include/mach/map.h |1 +
arch/arm/mach-exynos/mach-exynos5-dt.c |2 ++
3
On Tue, Dec 18, 2012 at 9:19 AM, Borislav Petkov wrote:
> On Tue, Dec 18, 2012 at 10:07:02AM -0500, Jeff Layton wrote:
>> Yeah, not many do, but presumably they'll set it once and forget about
>> it. Once someone straightens them out, they should rarely break.
>>
>> OTOH, the value of defaulting
On Mon, Dec 17, 2012 at 03:38:56PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Now the event grouping viewing requires linking all member hists in a
> group to the leader's. Thus hists__output_resort should be called
> after linking all events in evlist.
>
> Introduce
Hiroshi Doyu wrote @ Tue, 18 Dec 2012 17:15:46 +0200 (EET):
> Rob Herring wrote @ Tue, 18 Dec 2012 14:46:36 +0100:
>
> > On 12/18/2012 03:21 AM, Hiroshi Doyu wrote:
> > > Hi Rob,
> > >
> > > Rob Herring wrote @ Mon, 17 Dec 2012 15:00:46
> > > +0100:
> > >
> > >> On 12/17/2012 12:18 AM,
Hello,
If there is no comments, what about applying the patch?
Regards,
Dmitry
On Wed, Dec 5, 2012 at 1:06 PM, Kasatkin, Dmitry
wrote:
> Hello,
>
> Any comments?
>
> - Dmitry
>
>
> On Mon, Nov 26, 2012 at 4:39 PM, Dmitry Kasatkin
> wrote:
>> Device-mapper "integrity" target provides
On Mon, Dec 17, 2012 at 03:38:52PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Add a few of group-related field in struct perf_{evlist,evsel} so that
> the group information in a evlist can be known easily. It only counts
> groups which have more than 1 members since leader-only groups
On Mon, Dec 17, 2012 at 03:38:53PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> As some new fields for handling groups added, check them to be sure to
> have valid values in test__group* cases.
>
> Cc: Jiri Olsa
Acked-by: Jiri Olsa
--
To unsubscribe from this list: send the line
On Tue, Dec 18, 2012 at 11:29:34AM -0500, Jun Chen wrote:
> * @master: Controller to which device is connected
> + * device_was_children_of_master is flag which the device is registed
> + * as the children of the bus
This isn't a kerneldoc style comment (it needs the @XXX: format). The
name
On Tue, Dec 18, 2012 at 08:40:26PM +0530, Vivek Gautam wrote:
> Adding support for USB3.0 phy for dwc3 controller on
> exynos5250 SOC.
>
> Signed-off-by: Vivek Gautam
> ---
> drivers/usb/phy/samsung-usbphy.c | 339
> +-
let's make the phy names standard
On Tue 18-12-12 15:22:23, azurIt wrote:
> >It should mitigate the problem. The real fix shouldn't be that specific
> >(as per discussion in other thread). The chance this will get upstream
> >is not big and that means that it will not get to the stable tree
> >either.
>
>
> OOM is no longer
On Wed, Nov 21, 2012 at 7:53 AM, Alan Cox wrote:
> On Wed, 21 Nov 2012 07:45:45 -0500
> Josh Boyer wrote:
>
>> On Fri, Nov 16, 2012 at 2:27 PM, Alan Cox wrote:
>> >
>> > [The fb maintainer appears to be absent at the moment].
>> >
>> > This is needed to fix a pile of lockdep splats that now
On Tue, Dec 18, 2012 at 10:07:02AM -0500, Jeff Layton wrote:
> Yeah, not many do, but presumably they'll set it once and forget about
> it. Once someone straightens them out, they should rarely break.
>
> OTOH, the value of defaulting to "N" is pretty low here. Maybe it
> would just be best to
On 12/17/2012 01:12 PM, Johannes Weiner wrote:
> A swappiness of 0 has a slightly different meaning for global reclaim
> (may swap if file cache really low) and memory cgroup reclaim (never
> swap, ever).
>
> In addition, global reclaim at highest priority will scan all LRU
> lists equal to
Rob Herring wrote @ Tue, 18 Dec 2012 14:46:36 +0100:
> On 12/18/2012 03:21 AM, Hiroshi Doyu wrote:
> > Hi Rob,
> >
> > Rob Herring wrote @ Mon, 17 Dec 2012 15:00:46 +0100:
> >
> >> On 12/17/2012 12:18 AM, Hiroshi Doyu wrote:
> >>> Set Snoop Control Unit(SCU) register base address dynamically
Hi Olof,
Le 18/12/2012 07:55, Olof Johansson a écrit :
> Maxime Ripard (1):
> ARM: sunxi: Change device tree naming scheme for sunxi
There's something odd about this one (commit 68136b10). The patch that
you seem to have applied differs from the one I sent. The DTs files
appears to have
On Tue, 18 Dec 2012 15:44:52 +0100
Borislav Petkov wrote:
> On Tue, Dec 18, 2012 at 07:13:17AM -0500, Jeff Layton wrote:
> > I agree that we often need cifsFYI debug info in order to troubleshoot
> > problems. The question here though is whether compiling those in ought
> > to be the default.
>
Hi list,
commit 263a523d18bca306016d75f5c8d5c57c37fe52fb changes the code of
DIV_ROUND_CLOSEST in include/linux/kernel.h to fix a compile time warning.
But now feeding in a zero into this macro results into 4198403. Tested with
gcc 4.4.3 and 4.7.2, on arch x86 and ARM.
I can reproduce this
Adding support for USB3.0 phy for dwc3 controller on
exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/samsung-usbphy.c | 339 +-
1 files changed, 337 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/samsung-usbphy.c
Changes form v1:
- Moved architecture related patch out of this patch-set.
- Replaced unnecessary multi-line macro definitions by
single line definitions.
- Creating new data structure for USB 3.0 phy type and embedding
it in 'samsung_usbphy' structure.
- Adding a flag in
On Tue, Dec 18, 2012 at 03:32:15PM +0100, Paolo Bonzini wrote:
> Il 18/12/2012 14:59, Michael S. Tsirkin ha scritto:
> >>> Can't we track state internally to the virtqueue? Exposing it
> >>> seems to buy us nothing since you can't call add_buf between
> >>> start and end anyway.
> >>
> >> I
On Tue, Dec 18, 2012 at 03:08:08PM +0100, Paolo Bonzini wrote:
> Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
> >> -static int virtscsi_queuecommand(struct Scsi_Host *sh, struct scsi_cmnd
> >> *sc)
> >> +static int virtscsi_queuecommand(struct virtio_scsi *vscsi,
> >> +
Before waking up the tty line discipline idle queue first check if the queue is
active (non empty). This prevents unnecessary entering the critical section in
the wake_up() function and therefore avoid needless scheduling overhead on a
PREEMPT_RT system caused by two processes being in the same
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-linus-3.8-rc0-bugfix-tag
which has two fixes. One of them is caused by the recent change introduced
by the 'x86-bsp-hotplug-for-linus' tip tree that inhibited bootup (old
On Tue, Dec 18, 2012 at 07:13:17AM -0500, Jeff Layton wrote:
> I agree that we often need cifsFYI debug info in order to troubleshoot
> problems. The question here though is whether compiling those in ought
> to be the default.
>
> In generic distro kernels, I think we do want that turned on even
Hello,
I'm sorry for the delay, I've been terribly busy recently.
On 12/11/2012 2:54 PM, Federico Vaga wrote:
> This allocator is needed because some device (like STA2X11 VIP) cannot
> work
> with DMA sg or DMA coherent. Some other device (like the one used by
> Jonathan when he proposes
Adding the phy-driver to ohci-exynos. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
drivers/usb/host/ohci-exynos.c | 70
1 files changed, 49
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
drivers/usb/host/ehci-s5p.c | 70 ++-
1 files changed, 49
This patch adds host phy support to samsung-usbphy.c and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 25 +-
drivers/usb/phy/Kconfig|2
Updating the names of usb-phy types to more generic names:
USB_PHY_TYPE_DEIVCE & USB_PHY_TYPE_HOST; and further update
its dependencies.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ehci-s5p.c |9 +
drivers/usb/host/ohci-exynos.c |
Changes from v4:
- Moved architecture side changes out of this patch-set.
- Added support for multiple usbphy phandle parsing and
doing all pmu_isolation() and phy_cfg_sel() related changes
in samsung-usbphy driver only instead of architecture
as in v4 patch-set.
- Removed unnecessary
Il 18/12/2012 14:59, Michael S. Tsirkin ha scritto:
>>> Can't we track state internally to the virtqueue? Exposing it
>>> seems to buy us nothing since you can't call add_buf between
>>> start and end anyway.
>>
>> I wanted to keep the state for these functions separate from the
>> rest. I don't
Hi Mark,
On 12/17/2012 04:51 PM, Mark Rutland wrote:
>> +static int __devinit gpioblock_of_probe(struct platform_device *pdev)
>> +{
>> +struct device_node *block;
>> +unsigned *gpios;
>> +int ngpio;
>> +int ret;
>> +struct gpio_block *gb;
>> +
>> +
Hi Joe,
Can you make checkpatch.pl check that lines added to UAPI headers don't have
the form:
#include
or:
#include "uapi/..."
Such as these should be regarded as errors as they will likely break userspace
which shouldn't get to see any uapi/ directories.
An example of
>It should mitigate the problem. The real fix shouldn't be that specific
>(as per discussion in other thread). The chance this will get upstream
>is not big and that means that it will not get to the stable tree
>either.
OOM is no longer killing processes outside target cgroups, so everything
On 12/14/2012 10:20 AM, Maxim V. Patlasov wrote:
> Hi,
>
...
> The throughput on some commodity (rather feeble) server was (in MB/sec):
>
> original / patched
>
> dd reads:~322 / ~382
> dd writes: ~277 / ~288
>
> aio reads: ~380 / ~459
> aio writes: ~319 /
The following changes since commit
6f0c0580b70c89094b3422ba81118c7b959c7556:
Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
are available in the git repository at:
git://openrisc.net/~jonas/linux tags/for-3.8
for you to fetch changes up to 634bd40a894d64df09ba36c12bb6e70787989ba9:
openrisc:
On 12/18/2012 03:21 AM, Hiroshi Doyu wrote:
> Hi Rob,
>
> Rob Herring wrote @ Mon, 17 Dec 2012 15:00:46 +0100:
>
>> On 12/17/2012 12:18 AM, Hiroshi Doyu wrote:
>>> Set Snoop Control Unit(SCU) register base address dynamically from DT.
>>>
>>> Signed-off-by: Hiroshi Doyu
>>> ---
>>>
On Tue, Dec 18, 2012 at 10:44:19AM +0800, fangxiaozhi 00110321 wrote:
> diff -uprN linux-3.7_bak/drivers/usb/storage/initializers.c
> linux-3.7/drivers/usb/storage/initializers.c
> --- linux-3.7_bak/drivers/usb/storage/initializers.c 2012-12-11
> 09:56:11.0 +0800
> +++
Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
>> -static int virtscsi_queuecommand(struct Scsi_Host *sh, struct scsi_cmnd *sc)
>> +static int virtscsi_queuecommand(struct virtio_scsi *vscsi,
>> + struct virtio_scsi_target_state *tgt,
>> +
On Tue, Dec 18, 2012 at 02:43:51PM +0100, Paolo Bonzini wrote:
> Il 18/12/2012 14:36, Michael S. Tsirkin ha scritto:
> > Some comments without arguing about whether the performance
> > benefit is worth it.
> >
> > On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
> >> diff --git
On Tue, Dec 18, 2012 at 01:32:52PM +0100, Paolo Bonzini wrote:
> This patch adds queue steering to virtio-scsi. When a target is sent
> multiple requests, we always drive them to the same queue so that FIFO
> processing order is kept. However, if a target was idle, we can choose
> a queue
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Changed the name of property for phy handler from'samsung,usb-phyctrl'
to 'samsung,usb-phyhandle' to make it look more generic.
Il 18/12/2012 14:36, Michael S. Tsirkin ha scritto:
> Some comments without arguing about whether the performance
> benefit is worth it.
>
> On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
>> diff --git a/include/linux/virtio.h b/include/linux/virtio.h
>> index cf8adb1..39d56c4
On Tue, Dec 18, 2012 at 01:32:47PM +0100, Paolo Bonzini wrote:
> Hi all,
>
> this series adds multiqueue support to the virtio-scsi driver, based
> on Jason Wang's work on virtio-net. It uses a simple queue steering
> algorithm that expects one queue per CPU. LUNs in the same target always
>
Il 18/12/2012 14:37, Michael S. Tsirkin ha scritto:
> On Tue, Dec 18, 2012 at 01:32:49PM +0100, Paolo Bonzini wrote:
>> Using the new virtio_scsi_add_sg function lets us simplify the queueing
>> path. In particular, all data protected by the tgt_lock is just gone
>> (multiqueue will find a new
On Tue, Dec 18, 2012 at 01:32:49PM +0100, Paolo Bonzini wrote:
> Using the new virtio_scsi_add_sg function lets us simplify the queueing
> path. In particular, all data protected by the tgt_lock is just gone
> (multiqueue will find a new use for the lock).
vq access still needs some protection:
Some comments without arguing about whether the performance
benefit is worth it.
On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
> diff --git a/include/linux/virtio.h b/include/linux/virtio.h
> index cf8adb1..39d56c4 100644
> --- a/include/linux/virtio.h
> +++
On Tue, Dec 04, 2012 at 10:35:13AM +0800, Li Zhong wrote:
> This patch adds user eqs exception hooks for async page fault page not
> present code path, to exit the user eqs and re-enter it as necessary.
>
> Async page fault is different from other exceptions that it may be
> triggered from idle
> > Please note that I resigned from my position of i2c subsystem
> > maintainer, so I will not handle this. If you think this is important,
> > you'll have to resubmit and Wolfram will decide what he wants to do
> > about it.
>
> OK, I had the impression that the conclusion was that the danger
Liu, Jinsong wrote:
> Liu, Jinsong wrote:
>> Konrad Rzeszutek Wilk wrote:
>>> On Thu, Dec 06, 2012 at 04:27:36AM +, Liu, Jinsong wrote:
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index
126d8ce..abd0396 100644 --- a/drivers/xen/Kconfig
+++
Add STEriccson DBX500 PRCM mailbox support.
Signed-off-by: Loic Pallardy
---
drivers/mailbox/Kconfig | 18 +-
drivers/mailbox/Makefile | 1 +
drivers/mailbox/mailbox-dbx500.c | 601 +++
TX: replace spin by mutex
RX: replace spin_lock_irq by spin_lock_irqsave
Signed-off-by: Loic Pallardy
---
drivers/mailbox/mailbox.c | 10 ++
drivers/mailbox/mailbox.h | 1 +
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/mailbox/mailbox.c
For debug purpose, mailbox must be available when
interrupts are disabled to collect dump information.
Signed-off-by: Loic Pallardy
---
drivers/mailbox/mailbox.c | 66 +++
include/linux/mailbox.h | 3 +++
2 files changed, 69 insertions(+)
diff
In order to create a generic mailbox framework, functions
and structures should be renamed in mailbox.
Signed-off-by: Loic Pallardy
---
drivers/mailbox/Kconfig | 3 +-
drivers/mailbox/mailbox-omap1.c | 28 -
drivers/mailbox/mailbox-omap2.c | 60 +-
Some mailboxes are made up of cross interrupts
and associated shared memory.
Shared memory mapping is fixed and cross interrupt/shared
memory relation make impossible the use of virtio.
Mailbox framework must be enough opened to support
any kind of mailbox.
Signed-off-by: Loic Pallardy
---
Actually moving it from plat-omap, as this framework/driver code is
supposed to be under drivers/ folder. The framework should work with
the current supported OMAP processors (OMAP1+) that have mailbox and
can be used as a method of interprocessor communication.
The mailbox hardware (in OMAP)
Current message type is a u32 to fit HW fifo format.
This should be extended to support any message exchanges
and type of mailbox.
Propose structure owns the original u32 and an optional
pointer on additional data.
Signed-off-by: Loic Pallardy
---
drivers/mailbox/Kconfig | 9 ++
OMAP and ST-Ericsson platforms are both using mailbox to communicate
with some coprocessors.
Based on OMAP existing mailbox framework, this series proposes a
generic framework, living under drivers/mailbox.
This series:
- moves omap-mailbox framework to a newly drivers/mailbox folder
(part of
Now internal structures can remain hidden to the user and just API
related functions and defines are made available.
Signed-off-by: Omar Ramirez Luna
---
drivers/mailbox/mailbox.c | 34 ++
drivers/mailbox/mailbox.h | 44
Coprocessor must be accessible during suspend transitions.
Signed-off-by: Loic Pallardy
---
drivers/mailbox/mailbox.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
index c0a8e49..57cb566 100644
---
On Tuesday 18 December 2012 12:37 PM, Prashant Gaikwad wrote:
On Tuesday 18 December 2012 11:54 AM, Laxman Dewangan wrote:
On Tuesday 18 December 2012 11:44 AM, Prashant Gaikwad wrote:
My clock driver rework includes this fix. Divider supports both DIVU71
and DIVU151.
UART divider is set to
Does anobody can helps me?
Hello. I'm newbie with cgroups (try to use blkio cgroups).
I need to shape disk activity on xen vps.
Each xen domU have block device that is software raid 1.
This raid have two devices that is lvm volume lies on srp (infiniband)
attached disk.
How can i limit disk usage
Hi Linus,
Please pull the latest SLAB tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git slab/for-linus
This contains preparational work from Christoph Lameter and Glauber Costa for
SLAB memcg and cleanups and improvements from Ezequiel Garcia and Joonsoo Kim.
Please
Whitespace at the end of line is not end of the world,
but nor useful too.
Signed-off-by: Michal Privoznik
---
Documentation/networking/tuntap.txt | 64 ++---
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git a/Documentation/networking/tuntap.txt
Hi all,
this series adds multiqueue support to the virtio-scsi driver, based
on Jason Wang's work on virtio-net. It uses a simple queue steering
algorithm that expects one queue per CPU. LUNs in the same target always
use the same queue (so that commands are not reordered); queue switching
virtio_scsi_target_state is now empty, but we will find new uses
for it in the next few patches. However, dropping the sglist lets
us turn the array-of-pointers into a simple array, which simplifies
the allocation.
However, we do not leave the virtio_scsi_target_state structs in the
flexible
On Tue, 2012-12-18 at 03:06 -0500, Tomas Hozza wrote:
> - Original Message -
> > > This is just for sanity. The value PATH_MAX was chosen after
> > > discussion
> > > with K. Y. Srinivasan and Olaf Hering instead of some "magic"
> > > number like
> > > 256 or 512.
> >
> > PATH_MAX is a
On Tue, 18 Dec 2012, Jean Delvare wrote:
> Hi Julia,
>
> On Thu, 11 Oct 2012 08:45:43 +0200 (CEST), Julia Lawall wrote:
> > I found 6 cases where there are more than 2 messages in the array. I
> > didn't check how many cases where there are two messages but there is
> > something other than
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for the lock).
The speedup is relatively small (2-4%) but it is worthwhile because of
the code simplification---both in
This will be needed soon in order to retrieve the per-target
struct.
Signed-off-by: Paolo Bonzini
---
drivers/scsi/virtio_scsi.c | 17 +
1 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
index
This patch adds queue steering to virtio-scsi. When a target is sent
multiple requests, we always drive them to the same queue so that FIFO
processing order is kept. However, if a target was idle, we can choose
a queue arbitrarily. In this case the queue is chosen according to the
current VCPU,
The virtqueue_add_buf function has two limitations:
1) it requires the caller to provide all the buffers in a single call;
2) it does not support chained scatterlists: the buffers must be
provided as an array of struct scatterlist;
Because of these limitations, virtio-scsi has to copy each
On 2012-12-15, at 19:15, Dave Chinner wrote:
>
> On Sat, Dec 15, 2012 at 11:25:23PM +0800, ys wrote:
>> From 3d56c131b58a21c05bcd677b9d2ba915abcbf195 Mon Sep 17 00:00:00 2001
>> From: yangsheng
>> Date: Sat, 15 Dec 2012 21:46:22 +0800
>> Subject: [PATCH] vfs: update atimes over one day in the
On Mon, 17 Dec 2012 09:30:33 -0600
Steve French wrote:
> I don't think taking out debugging makes sense - we need debugging a
> lot more often than expected even to diagnose user errors (usually
> relating to session establishment failures, since we are very limited
> in how much information can
On Tue, 18 Dec 2012 12:59:26 +0100, Wolfram Sang wrote:
>
> > I reviewed this patch 3 months ago and did not hear back. Are you going
> > to update this patch and resubmit, or should I just drop it?
>
> Uwe is on holiday. I'll take care about it if the need is still there...
The need was Uwe's
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer tick broadcast
mechanism.
Signed-off-by: Mark Rutland
---
arch/arm/Kconfig |1 +
arch/arm/kernel/smp.c |3 +--
2 files changed, 2 insertions(+), 2
Currently, the timer broadcast mechanism is defined by a function
pointer on struct clock_event_device. As the fundamental mechanism for
broadcast is architecture-specific, this means that clock_event_device
drivers cannot be shared across multiple architectures.
This patch adds an (optional)
Currently, the ARM backend must maintain a redundant list of timers for
the purpose of centralising timer broadcast functionality. This prevents
sharing timer drivers across architectures.
This patch moves the pain of dealing with timer broadcasts to the core
clockevents tick broadcast code,
Currently we only provide an implementation of smp_timer_broadcast in
smp.c if GENERIC_CLOCKEVENTS_BROADCAST is selected. As
smp_timer_broadcast is only used in smp.c, smp.c depends on SMP, and
GENERIC_CLOCKEVENTS_BROADCAST is selected by SMP, this is unnecessary.
This patch removes the redundant
Currently the broadcast mechanism used for timers is abstracted by a
function pointer on struct clock_event_device. As the fundamental
mechanism for broadcast is architecture-specific, this ties each
clock_event_device driver to a single architecture, even where the
driver is otherwise generic.
301 - 400 of 932 matches
Mail list logo
