From: Nicholas Bellinger
This patch adds a virtio_scsi_cmd_req_pi header as recommened by
Paolo that contains do_pi_niov + di_pi_niov elements used for
signaling when protection information buffers are expected to
preceed the data buffers.
Cc: Paolo Bonzini
Cc: Michael S. Tsirkin
Cc: Martin
From: Nicholas Bellinger
Hi MST, MKP, Paolo & Co,
This is an updated -v2 series for adding T1O protection information (PI)
SGL passthrough support between virtio-scsi LLD + vhost-scsi fabric
endpoints.
The patch series is available at:
From: Nicholas Bellinger
This patch updates vhost_scsi_handle_vq() to check for the existance
of virtio_scsi_cmd_req_pi comparing vq->iov[0].iov_len in order to
calculate seperate data + protection SGLs from data_num.
Also update tcm_vhost_submission_work() to pass the pre-allocated
From: Nicholas Bellinger
This patch updates tcm_vhost_make_nexus() to pre-allocate per descriptor
tcm_vhost_cmd->tvc_prot_sgl[] used to expose protection SGLs from within
virtio-scsi guest memory to vhost-scsi.
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Martin K. Petersen
Cc: Christoph
From: Nicholas Bellinger
This patch adds vhost_scsi_map_iov_to_prot() to perform the mapping of
T10 data integrity memory between virtio iov + struct scatterlist using
get_user_pages_fast() following existing code.
As with vhost_scsi_map_iov_to_sgl(), this does sanity checks against the
total
From: Nicholas Bellinger
This patch adds a VIRTIO_SCSI_F_T10_PI feature bit for signaling
host support of accepting T10 protection information SGLs from
virtio-scsi guest.
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Martin K. Petersen
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi
From: Nicholas Bellinger
Move the overflow check for sgl_count > TCM_VHOST_PREALLOC_SGLS into
vhost_scsi_map_iov_to_sgl() so that it's based on the total number
of SGLs for all IOVs, instead of single IOVs.
Also, rename TCM_VHOST_PREALLOC_PAGES -> TCM_VHOST_PREALLOC_UPAGES
to better describe
From: Nicholas Bellinger
This patch updates virtscsi_probe() to setup necessary Scsi_Host
level protection resources. (currently hardcoded to 1)
It changes virtscsi_add_cmd() to attach outgoing / incoming
protection SGLs preceeding the data payload, and is using the
new
Gentle reminder for reviewing this and i-g-t patch.
On Mon, 2014-03-10 at 17:06 +0530, sagar.a.kam...@intel.com wrote:
> From: Sagar Kamble
>
> With this patch we allow larger cursor planes of sizes 128x128
> and 256x256.
>
> v2: Added more precise check on size while setting cursor plane.
>
On Mon, Mar 17, 2014 at 11:12:15AM +1030, Rusty Russell wrote:
>
> Note that with indirect descriptors (which is supported by Almost
> Everyone), we can actually use the full index, so this value is a bit
> pessimistic. But it's OK as a starting point.
So is this something that can go upstream
Hi all,
Today's linux-next merge of the tip tree got a conflict in
drivers/clocksource/Kconfig between commit 3f8e8cee2f4b ("clocksource:
qcom: Move clocksource code out of mach-msm") from the arm-soc tree and
commit fd3f1270d237 ("clocksource: Add Kconfig entries for CMT, MTU2, TMU
and STI")
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm/mach-zynq/Kconfig between commit ddb902cc3459 ("ARM: centralize
common multi-platform kconfig options") from the arm-soc tree and commit
cd325295871f ("arm: zynq: Add support for cpufreq") from the tip tree.
I fixed it
Hi Tomasz,
On 03/17/2014 11:51 AM, Chanwoo Choi wrote:
> Hi Tomasz,
>
> On 03/15/2014 02:42 AM, Tomasz Figa wrote:
>> Hi Chanwoo,
>>
>> On 13.03.2014 09:17, Chanwoo Choi wrote:
>>> There are not the clock controller of ppmudmc0/1. This patch control the
>>> clock
>>> of ppmudmc0/1 which is used
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm/mach-shmobile/Kconfig between commit 4a51856b4267 ("ARM:
shmobile: Use 64-bit dma_addr_t on r8a7790/r8a7791") from the renesas
tree and commit aeb8fb7910fc ("ARM: shmobile: Remove CMT, TMU and STI
Kconfig entries") from
Added EDAC support for reporting the ecc errors of synopsys ddr controller.
The ddr ecc controller corrects single bit errors and detects double bit
errors
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes for v2:
- Updated the commit header and message
- Renamed the filenames to
Hi Tomasz,
On 03/15/2014 02:35 AM, Tomasz Figa wrote:
> Hi Chanwoo, Mark,
>
> On 14.03.2014 11:56, Chanwoo Choi wrote:
>> Hi Mark,
>>
>> On 03/14/2014 07:35 PM, Mark Rutland wrote:
>>> On Fri, Mar 14, 2014 at 07:14:37AM +, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014 02:53 AM,
Hi Tomasz,
On 03/15/2014 02:49 AM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 13.03.2014 09:17, Chanwoo Choi wrote:
>> This patch fix bug about resource leak when happening probe fail and code
>> clean
>> to add debug message.
>>
>> Signed-off-by: Chanwoo Choi
>> ---
>>
On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote:
> Erk, our tests are insufficient. Testbuilding an allmodconfig with this
> now:
Good idea.
> diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
[]
> @@ -188,6 +188,9 @@ struct kparam_array
> /* Default value
Hi,
I am studying Linux CFS recently. After numerous searches, I am still
unable to get rid of the following question. Finally I decide to bother
this group for the answer.
In group scheduling, sched_entity can represent both "task group" and "task",
indicated by "se->my_q".
When CFS tries to
Hi Jiri,
On Fri, 14 Mar 2014 15:00:02 +0100, Jiri Olsa wrote:
> +static int thread_init(struct thread_data *td)
> +{
> + void *map;
> +
> + map = mmap(NULL, page_size, PROT_READ|PROT_WRITE,
> +MAP_SHARED|MAP_ANONYMOUS, -1, 0);
Shouldn't it be an executable mapping to be
On Wed, Mar 12, 2014 at 01:00:51PM +0100, Michal Simek wrote:
> Hi Olof,
>
> >> diff --git a/Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocm.txt
> >> b/Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocm.txt
> >> new file mode 100644
> >> index 000..64cb5e8
> >> --- /dev/null
>
On Thu, Mar 13, 2014 at 05:16:52AM +0800, Santosh Shilimkar wrote:
> On Thursday 13 March 2014 12:00 AM, Vinod Koul wrote:
> > On Wed, Mar 12, 2014 at 03:50:32AM +0800, Santosh Shilimkar wrote:
> >> On Tuesday 11 March 2014 06:23 PM, Vinod Koul wrote:
> >>> On Fri, Feb 28, 2014 at 05:56:40PM
Theodore Ts'o writes:
> On Fri, Mar 14, 2014 at 10:38:40AM -0700, Joe Perches wrote:
>> > +static int queue_depth = 64;
>> > +module_param(queue_depth, int, 444);
>>
>> 444? Really Ted?
>
> Oops, *blush*. Thanks for catching that.
Erk, our tests are insufficient. Testbuilding an
Steven Rostedt writes:
> On Wed, 26 Feb 2014 14:01:43 -0500
> Hi Rusty,
>
> This patch doesn't need to be stable, and can wait till v3.15. But I
> have other patches that will break with this patch (headers that needed
> to include tracepoint.h and not depend on a header chain to include it).
>
>
beh...@converseincode.com writes:
> From: Mark Charlebois
>
> This code makes a compile time type check that is optimized away. Clang
> complains that it generates an unused function:
Thanks, applied.
Cheers,
Rusty.
>
> linux/kernel/panic.c:471:1: warning: unused function '__check_panic'
>
Kees Cook writes:
> On Wed, Mar 12, 2014 at 8:40 PM, Rusty Russell wrote:
>> Kees Cook writes:
>>> Why not just do this with 0-base-address detection like my v2? That
>>> would mean we don't need to remember to add this flag in the future to
>>> imagined new architectures that might want this
Josh Triplett writes:
> On Tue, Mar 11, 2014 at 12:31:33PM -0700, Andrew Morton wrote:
> I'd love to do that, but as far as I can tell, VIRTIO_BALLOON has gone
> out of its way to support !CONFIG_BALLOON_COMPACTION.
>
> Could someone who works on VIRTIO_BALLOON provide some details here
> about
On 03/16/2014 09:12 PM, Sarah Newman wrote:
>
> Unconditional eager allocation works. Can xen users count on this being
> included and applied to the
> stable kernels?
>
I don't know. If we state that it is a bug fix for Xen it might be
possible, but it would be up to Greg (Cc:'d) and the
From: Robert Moore
It is reported that the auto-serialization mechanism has broken some
machine. This patch fixes the issues by igoring the SyncLevel
attribute of the marked Method.
References: http://www.spinics.net/lists/linux-acpi/msg49496.html
Reported-by: Valdis Kletnieks
Reported-by:
This feature enabled by the following commit is still under development.
Commit: cd52379678785b02d7a357988cfba214fdaf92f4
Subject: ACPICA: Add global option to disable method auto-serialization.
This change adds an option to disable the auto-serialization of
methods that create named
Hi Daniel,
Thanks for the patch.
On 17 March 2014 08:58, Daniel Kurtz wrote:
> The following commit [0] fixed a use-after-free, but left the subdrv open
> in the error path.
>
> [0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
> drm/exynos: Fix freeing issues in exynos_drm_drv.c
>
>
It is reported that the auto-serialization mechanism has broken some
machine. A patch in this series tries to fix the reported issue, it is
sent to the reporter for verification, thus marked as RFC.
Since this feature may still need to be validated, we can disable it
temporarily in order not to
On 03/16/2014 08:43 PM, H. Peter Anvin wrote:
> On 03/16/2014 08:35 PM, Sarah Newman wrote:
>> Can you please review my patch first? It's only enabled when absolutely
>> required.
>
> It doesn't help. It means you're running on Xen, and you will have
> processes subjected to random SIGKILL
They don't have to be atomic_t, because they are simple boolean
toggles.
Signed-off-by: Li Zefan
---
mm/kmemleak.c | 78 +--
1 file changed, 39 insertions(+), 39 deletions(-)
diff --git a/mm/kmemleak.c b/mm/kmemleak.c
index
- remove kmemleak_padding().
- remove kmemleak_release().
Signed-off-by: Li Zefan
---
include/linux/kmemleak.h | 2 --
mm/kmemleak.c| 7 +--
2 files changed, 1 insertion(+), 8 deletions(-)
diff --git a/include/linux/kmemleak.h b/include/linux/kmemleak.h
index 2a5e554..5bb4246
Currently if kmemleak is disabled, the kmemleak objects can never be freed,
no matter if it's disabled by a user or due to fatal errors.
Those objects can be a big waste of memory.
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
1200264 1197433 99%0.30K 46164 26
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
fs/bio-integrity.c between commit eec70897d81b ("bio-integrity: Drop
bio_integrity_verify BUG_ON in post bip->bip_iter world") from Linus'
tree and commit bf36f9cfa6d3 ("fs/bio-integrity: remove duplicate code")
from the block
On 03/16/2014 07:07 PM, Axel Lin wrote:
2014-03-17 9:47 GMT+08:00 Guenter Roeck :
Commit 09e99bca8 (spi: sc18is602: Convert to let spi core validate
transfer speed) made the maximum transfer speed much more restrictive
than before. The transfer speed used to be adjusted to 1/4 of the chip
clock
> Subject: [PATCH v3 0/4] ASoC: simple-card: multi DAI links extension
>
> This patch series extends the simple card driver to handle
> many DAI links as this exists in the Cubox audio subsystem.
>
> -v3
> - remove 'Fix the reference count of device nodes'
> which is applied
Apsveicam Uzvarētājs - Ref Nē: Sp/229/0-01/07/5-02/ES.
Jūsu e-pasts ID ir tikko ieguva € 450,000.00 Eiro(četri simti piecdesmit
tūkstoši. Eiro) uz Uplift Starptautiskā Labdarības programma. Ref Nr
Sp/229/0-01/07/5-02/ES. Lucky Nr 9/11/13/24/40.
Lai iegūtu vairāk informācijas un kontaktu
On 03/16/2014 08:35 PM, Sarah Newman wrote:
> Can you please review my patch first? It's only enabled when absolutely
> required.
It doesn't help. It means you're running on Xen, and you will have
processes subjected to random SIGKILL because they happen to touch the
FPU when the atomic pool
Can you please review my patch first? It's only enabled when absolutely
required.
On 03/16/2014 08:33 PM, H. Peter Anvin wrote:
> No, the right thing is to unf*ck the Xen braindamage and use eagerfpu as a
> workaround for the legacy hypervisor versions.
>
> GFP_ATOMIC -> SIGKILL is definitely
No, the right thing is to unf*ck the Xen braindamage and use eagerfpu as a
workaround for the legacy hypervisor versions.
GFP_ATOMIC -> SIGKILL is definitely a NAK.
On March 16, 2014 8:13:05 PM PDT, Sarah Newman wrote:
>On 03/10/2014 10:15 AM, David Vrabel wrote:
>> On 10/03/14 16:40, H. Peter
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Signed-off-by: Daniel Kurtz
---
Hi, I noticed this when reviewing some recent patches.
I am only
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Change-Id: I452e944bf090fb11434d9e34213c890c41c15d73
Signed-off-by: Daniel Kurtz
---
The xen PVABI dictates that CR0 TS will be automatically cleared for
the device not available trap. This means it is not safe to task
switch with the default PVABI behavior.
One method of working around this is to disallow scheduling when
allocating memory for the fpu state, but in extremely low
On 03/13/2014 01:57 PM, Alex Shi wrote:
> In the cpu_load decay usage, we mixed the long term, short term load with
> balance bias, randomly pick a big/small value from them according to balance
> destination or source. This mix is wrong, the balance bias should be based
> on task moving cost
On 03/10/2014 10:15 AM, David Vrabel wrote:
> On 10/03/14 16:40, H. Peter Anvin wrote:
>> On 03/10/2014 09:17 AM, David Vrabel wrote:
>>> math_state_restore() is called from the #NM exception handler. It may
>>> do a GFP_KERNEL allocation (in init_fpu()) which may schedule.
>>>
>>> Change this
On 2014/3/13 20:14, Catalin Marinas wrote:
> On Thu, Mar 13, 2014 at 06:47:46AM +, Li Zefan wrote:
>> +Freeing kmemleak internal objects
>> +-
>> +
>> +To allow access to previosuly found memory leaks even when an error fatal
>> +to kmemleak happens, internal
Hi Heikki,
Thank you for your reply.
(2014/03/14 23:16), Heikki Krogerus wrote:
Hi,
On Fri, Mar 14, 2014 at 11:21:54AM +0900, Yoshihiro YUNOMAE wrote:
void serial8250_clear_and_reinit_fifos(struct uart_8250_port *p)
{
- unsigned char fcr;
-
serial8250_clear_fifos(p);
-
Hi Tomasz,
On 03/15/2014 02:52 AM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 13.03.2014 09:17, Chanwoo Choi wrote:
>> This patch disable ppmu clocks before entering suspend state to remove
>> power-leakage and enable ppmu clocks on resume function.
>
> I don't think there is any need for this,
Hi Tomasz,
On 03/15/2014 02:42 AM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 13.03.2014 09:17, Chanwoo Choi wrote:
>> There are not the clock controller of ppmudmc0/1. This patch control the
>> clock
>> of ppmudmc0/1 which is used for monitoring memory bus utilization.
>>
>> Also, this patch code
--
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
Please read the FAQ at http://www.tux.org/lkml/
Thanks for your replies, I've applied your suggestions to the patch.
Davide
Fixed some line over 80 characters.
From: Davide Berardi
Signed-off-by: Davide Berardi
---
drivers/staging/line6/driver.c | 54 ++---
drivers/staging/line6/usbdefs.h | 2 +-
2
Hi Jiri,
Today's linux-next merge of the hid tree got a conflict in
drivers/hid/i2c-hid/i2c-hid.c between commit 9d27f43274e4 ("HID: fix
buffer allocations") from Linus' tree and commit 649f94790314 ("HID:
i2c-hid: use generic .request() implementation") from the hid tree.
I fixed it up (the
The original segment_info's show looks out-of-format:
cat /proc/fs/f2fs/loop0/segment_info
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 512
512 512 512 512 512 512 512 0 0 512
348 0 263 0 0 512 0 0 512 512
What a difference a week makes. In a good way. A week ago, cutting
rc6, I was not a happy person: the release had much too much noise in
it, and I felt that an rc8 and even an rc9 might well be a real
possibility.
Now it's a week later, and rc7 looks much better. Yeah, there's random
stuff all
Hi Gu,
> -Original Message-
> From: Gu Zheng [mailto:guz.f...@cn.fujitsu.com]
> Sent: Thursday, March 13, 2014 5:58 PM
> To: Chao Yu
> Cc: 'Kim'; 'linux-kernel'; 'f2fs'
> Subject: Re: [f2fs-dev] [PATCH 3/5] f2fs: format segment_info's show for
> better legibility
>
> Hi,
> On 03/13/2014
On 03/04/2014 02:39 PM, Matt Mackall wrote:
>
> [temporarily coming out of retirement to provide a clue]
>
> The pool mixing function is intentionally _reversible_. This is a
> crucial security property.
>
> That means, if I have an initial secret pool state X, and hostile
> attacker controlled
On 03/15/2014 09:46 AM, Fengguang Wu wrote:
> Alex, we noticed the below changes in
>
> https://github.com/alexshi/power-scheduling.git single-balance
> commit e1f728f230025ba2f2ed71e19b156291f53b68fe ("sched/balance: replace
> idle_balance")
>
Thanks a lot for your data! But I am wondering
Raghavendra K T writes:
> On 02/18/2014 03:19 PM, Jan Kara wrote:
>> On Tue 18-02-14 12:55:38, Raghavendra K T wrote:
>>> Currently max_sane_readahead() returns zero on the cpu having no local
>>> memory node
>>> which leads to readahead failure. Fix the readahead failure by returning
>>>
2014-03-17 9:47 GMT+08:00 Guenter Roeck :
> Commit 09e99bca8 (spi: sc18is602: Convert to let spi core validate
> transfer speed) made the maximum transfer speed much more restrictive
> than before. The transfer speed used to be adjusted to 1/4 of the chip
> clock rate if a higher transfer speed
Hi Tomasz,
On 03/15/2014 02:58 AM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 13.03.2014 09:17, Chanwoo Choi wrote:
>> This patchset support devicetree and use common ppmu driver instead of
>> individual code of exynos4_bus.c to remove duplicate code. Also this patchset
>> get the resources for
Hi,
On 03/14/2014 07:47 PM, Bartlomiej Zolnierkiewicz wrote:
> On Friday, March 14, 2014 12:14:03 PM Chanwoo Choi wrote:
>> Hi,
>>
>> On 03/14/2014 01:43 AM, Bartlomiej Zolnierkiewicz wrote:
>>>
>>> Hi,
>>>
>>> On Thursday, March 13, 2014 05:17:21 PM Chanwoo Choi wrote:
This patchset support
Dear Kukjin,
On 03/17/2014 10:44 AM, Kukjin Kim wrote:
> Chanwoo Choi wrote:
>>
>> Dear Kukjin,
>>
>> Ping.
>>
>> Please review this patchset.
>>
> Looks good to me, will apply tonight.
Thanks for your reply.
Best Regards,
Chanwoo Choi
--
To unsubscribe from this list: send the line
Commit 09e99bca8 (spi: sc18is602: Convert to let spi core validate
transfer speed) made the maximum transfer speed much more restrictive
than before. The transfer speed used to be adjusted to 1/4 of the chip
clock rate if a higher transfer speed was requested. Now such transfers are
simply
Hi Don,
On Fri, 14 Mar 2014 10:43:44 -0400, Don Zickus wrote:
> When trying to capture perf data on a system running spejbb2013,
> perf hung for about 15 minutes. This is because it took that
> long to gather about 10,000 thread maps and process them.
>
> I don't think a user wants to wait that
Chanwoo Choi wrote:
>
> Dear Kukjin,
>
> Ping.
>
> Please review this patchset.
>
Looks good to me, will apply tonight.
Thanks,
Kukjin
> Best Regards,
> Chanwoo Choi
>
> On 03/13/2014 10:57 AM, Chanwoo Choi wrote:
> > Dear Kukjin,
> >
> > On 03/12/2014 08:21 PM, Tomasz Figa wrote:
> >> Hi
The OASIS virtio-dev mailing list is a good place for implementers to
discuss details of the standard, but it requires subscription to avoid
IP issues :(
It makes more sense to stick with the
virtualizat...@lists.linux-foundation.org mailing list for bug
reports. We can refer to the OASIS list
Dear Kukjin,
Ping.
Please review this patchset.
Best Regards,
Chanwoo Choi
On 03/13/2014 10:57 AM, Chanwoo Choi wrote:
> Dear Kukjin,
>
> On 03/12/2014 08:21 PM, Tomasz Figa wrote:
>> Hi Chanwoo,
>>
>> On 12.03.2014 07:19, Chanwoo Choi wrote:
>>> This patch add missing dt data of Exynos4x12
Hi Jingoo,
On 03/17/2014 09:17 AM, Jingoo Han wrote:
> On Friday, March 14, 2014 6:30 PM, Chanwoo Choi wrote:
>>
>> This patch use SET_SYSTEM_SLEEP_PM_OPS macro instead of legacy method.
>>
>> Signed-off-by: Chanwoo Choi
>> ---
>> drivers/devfreq/exynos/exynos4_bus.c | 4 +++-
>> 1 file
Hi,
> From: Valdis Kletnieks [mailto:valdis.kletni...@vt.edu]
> Sent: Saturday, March 15, 2014 12:05 AM
>
> Surprisingly enough, this hasn't seemed to have bitten many Linux people yet,
> Google only finds a BSD thread (where the same ACPICA code is in use):
>
>
On 02/26/2014 11:42 AM, Pankaj Dubey wrote:
When compiled using ARM64 cross compiler, gcc complains as
drivers/clk/samsung/clk.c:293:18:
warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
Signed-off-by: Pankaj Dubey
---
drivers/clk/samsung/clk.c |2 +-
1
On 03/05/2014 08:12 PM, Pankaj Dubey wrote:
NO_IRQ may be defined as '(unsigned int) -1' in some architectures
(arm, sh ...), and either may not be defined in some architectures
(arm64) which can enable RTC_DRV_S3C.
Also since platform_get_irq returns err-code in case of any error,
we do not
Theodore Ts'o writes:
> The current virtio block sets a queue depth of 64, which is
> insufficient for very fast devices. It has been demonstrated that
> with a high IOPS device, using a queue depth of 256 can double the
> IOPS which can be sustained.
>
> As suggested by Venkatash Srinivas, set
Hi Andi,
On Thu, 13 Mar 2014 12:53:58 -0700, Andi Kleen wrote:
> +def MASK(bits):
> +return (1 << bits) - 1
> +
> +def decode_bits(val, names, bits, shift):
> +v = (val >> shift) & MASK(bits)
> +s = ""
> +for name, index in zip(names, range(0, len(names))):
> +if v & (1 <<
On Fri, 14 Mar 2014 13:20:23 +0100, Tomasz Figa wrote:
> Hi KyongHo,
>
> On 14.03.2014 06:06, Cho KyongHo wrote:
> > This patch adds dts entries for the System MMU devices found on
> > Exynos4 and Exynos5 SoC series and the System MMU binding
> > documentation.
> >
> > CC: Rob Herring
> > CC:
On Fri, 14 Mar 2014 13:17:26 +0100, Tomasz Figa wrote:
> Hi KyongHo,
>
> On 14.03.2014 06:06, Cho KyongHo wrote:
> > This adds gate clocks of all System MMUs and their master IPs
> > that are not apeared in clk-exynos5250.c and clk-exynos5420.c
> > Also fixes GATE_IP_ACP to 0x18800 and changed
On Fri, 14 Mar 2014 17:29:36 +0530, Sachin Kamat wrote:
> On 14 March 2014 17:19, Cho KyongHo wrote:
> >> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
> >> Sent: Friday, March 14, 2014 7:00 PM
> >>
> >> On 14 March 2014 10:31, Cho KyongHo wrote:
> >> > Commit 25e9d28d92 (ARM: EXYNOS:
On Friday, March 14, 2014 6:30 PM, Chanwoo Choi wrote:
>
> This patch use SET_SYSTEM_SLEEP_PM_OPS macro instead of legacy method.
>
> Signed-off-by: Chanwoo Choi
> ---
> drivers/devfreq/exynos/exynos4_bus.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
On Monday, March 17, 2014 01:09:39 AM Rafael J. Wysocki wrote:
> On Sunday, March 16, 2014 02:08:16 PM Stephane Eranian wrote:
> > Rafael,
> >
> > Thanks for the analysis.
> >
> > On Sun, Mar 16, 2014 at 12:55 PM, Borislav Petkov wrote:
> > > On Sat, Mar 15, 2014 at 03:15:04PM +0100, Rafael J.
On Fri, Mar 14, 2014 at 11:58:50PM +0100, Laura Abbott wrote:
> There's no need to have an architecture version of scatterlist.h
> if the only thing the file does is include asm-generic/scatterlist.h.
> Switch to the asm-generic versions directly.
>
> Cc: Mikael Starvik
For the CRIS-part:
On Sunday, March 16, 2014 02:08:16 PM Stephane Eranian wrote:
> Rafael,
>
> Thanks for the analysis.
>
> On Sun, Mar 16, 2014 at 12:55 PM, Borislav Petkov wrote:
> > On Sat, Mar 15, 2014 at 03:15:04PM +0100, Rafael J. Wysocki wrote:
> >> I've just gone throught this.
> >
> > Thanks.
> >
> >> So
On Sunday, March 16, 2014 10:41:35 PM Paul Bolle wrote:
> Rafael,
>
> 0) Ever since v3.14-rc1 I've noticed two new boot messages on an,
> outdated, ThinkPad X41:
> nsc-ircc, Found chip at base=0x164e
> nsc-ircc, Wrong chip version ff
>
> The first is printed at info level, so I would
Hi Greg,
On Tue, 11 Mar 2014 18:50:21 -0700 Greg KH wrote:
>
> On Wed, Mar 12, 2014 at 12:51:52AM +, Mark Brown wrote:
> >
> > After merging the driver-core tree, today's linux-next build ()
> > failed like this on a PowerPC defconfig:
> >
> > HEAD is now at ceb98e684dec Merge
Hi Greg,
On Sat, 15 Mar 2014 05:29:42 + Greg KH wrote:
>
> On Sat, Mar 15, 2014 at 01:57:29PM +1100, Benjamin Herrenschmidt wrote:
> >
> > It's messy. Stephen really doesn't like if we pull each other trees like
> > that unless they are topic branches. He also doesn't like when we keep
> >
On Sun, 2014-03-16 at 22:19 +, Winkler, Tomas wrote:
> > #define cl_dbg(dev, cl, format, arg...) \
> > dev_dbg(&(dev)->pdev->dev, MEI_CL_FMT format, MEI_CL_PRM(cl),
> > ##arg)
[]
> > #define cl_dbg(cl, format, ...) \
> > dev_dbg(&(cl)->dev)->pdev->dev, MEI_CL_FMT format,
On 03/03/2014 03:51 PM, Kees Cook wrote:
> When bringing a new RNG source online, it seems like it would make sense
> to use some of its bytes to make the system entropy pool more random,
> as done with all sorts of other devices that contain per-device or
> per-boot differences.
>
>
>
> On Sun, 2014-03-16 at 14:35 +0200, Tomas Winkler wrote:
> > use cl_dbg for debug log messages in cl context
>
> I think all the uses of cl_dbg and cl_err are odd.
>
> from: client.h
>
> #define cl_dbg(dev, cl, format, arg...) \
> dev_dbg(&(dev)->pdev->dev, MEI_CL_FMT format,
Hi
On Sun, Mar 16, 2014 at 8:17 PM, Ben Hutchings wrote:
> On Sun, 2014-03-16 at 18:21 +0100, David Herrmann wrote:
> [...]
>> --- a/include/linux/netdevice.h
>> +++ b/include/linux/netdevice.h
>> @@ -74,6 +74,11 @@ void netdev_set_default_ethtool_ops(struct net_device
>> *dev,
>> #define
Rafael,
0) Ever since v3.14-rc1 I've noticed two new boot messages on an,
outdated, ThinkPad X41:
nsc-ircc, Found chip at base=0x164e
nsc-ircc, Wrong chip version ff
The first is printed at info level, so I would have ignored it, but the
second is printed at error level.
1) I've finally
On Thu, 2014-03-13 at 17:45 +0800, Gu Zheng wrote:
> This patchset has been applied to linux-next, and these problems also exist
> in 3.12.y and 3.13.y stable tree.
> So please merge this patchset to 3.12.y and 3.13.y stable tree.
They must be in Linus's tree before they are acceptable for
On Sun, 2014-03-16 at 21:52 +0100, Fabian Frederick wrote:
> -Convert spinlock/stat array to va_format (inspired by Joe Perches help
> on previous logging patches).
> -Convert printk(KERN_ERR to pr_warn in __ntfs_warning.
> -Convert printk(KERN_ERR to pr_err in __ntfs_error.
> -Convert
-Convert spinlock/stat array to va_format (inspired by Joe Perches help
on previous logging patches).
-Convert printk(KERN_ERR to pr_warn in __ntfs_warning.
-Convert printk(KERN_ERR to pr_err in __ntfs_error.
-Convert printk(KERN_DEBUG to pr_debug in __ntfs_debug.
(__ntfs_debug behavior is
Commit bd2a31d522344 ("get rid of fget_light()") introduced the
__fdget_pos() function, which returns the resulting file pointer and
fdput flags combined in an 'unsigned long'. However, it also changed the
behavior to return files with FMODE_PATH set, which shouldn't happen
because read(),
On March 16, 2014 7:16:39 PM GMT+00:00, Alexandre Belloni
wrote:
>On 16/03/2014 at 18:16:54 +, Jonathan Cameron wrote :
>> On 05/03/14 17:35, Alexandre Belloni wrote:
>> >Old ADCs, as present on the sam9rl and the sam9g45 don't have a TSMR
>register
>> >and the touchscreen support should
Hi,
My external disk uses a Initio Corporation INIC-1618L SATA chip.
vendor/product are : 0x13fd/0x0840 and bcdDevice is 1.14 making the disk work
very slowly 12Mb in spite of 10 times faster. bcdUSB seem to be ok : 2.00
Tried this on 3.13 and 3.14-rc6
Is there a module to load specifically. In
Also, the difference it would make is fix the issue for when a
delayed_work is used for both immediate work (mod_delayed_work(0)) and
delayed work.
On Sun, Mar 16, 2014 at 12:13 PM, dbasehore . wrote:
> There's already behavior that is somewhat like that with the current
> implementation. If
On Sun, Mar 16, 2014 at 11:57 AM, Ben Hutchings wrote:
> On Fri, 2014-03-14 at 05:36 -0700, Luis R. Rodriguez wrote:
>> On Fri, Mar 14, 2014 at 1:45 AM, Kalle Valo wrote:
> [...]
>> > + NO LICENSES OR OTHER RIGHTS,
>> > +WHETHER EXPRESS, IMPLIED, BASED ON ESTOPPEL OR OTHERWISE, ARE GRANTED
>> >
Right now when people try to report issues in the kernel they send stack
dumps to eachother, which looks something like this:
[6.906437] [] ? backtrace_test_irq_callback+0x20/0x20
[6.907121] [] dump_stack+0x52/0x7f
[6.907640] [] backtrace_regression_test+0x38/0x110
[6.908281]
1 - 100 of 436 matches
Mail list logo
