[+cc Hannes, Ariel, LKML]
On Thu, Apr 14, 2016 at 11:42:05PM +0530, Hariprasad Shenai wrote:
> commit 104daa71b396 ("PCI: Determine actual VPD size on first access")
> introduced a regression in cxgb4 driver and used to fail in pci probe.
>
> The problem is stemming from the fact that the Chelsio
I am announcing the release of the Linux 3.13.11-ckt39 kernel.
***
*** Note that this is the FINAL 3.13.y-ckt RELEASE in this series.
***
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.c
diff --git a/Makefile b/Makefile
index fb90bd5..f60cc1c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 13
SUBLEVEL = 11
-EXTRAVERSION = -ckt38
+EXTRAVERSION = -ckt39
NAME = King of Alienated Frog Porn
# *DOCUMENTATION*
diff --git a/arch/parisc/kernel/parisc_ksy
On Fri, Apr 15, 2016 at 11:06 AM, Jeff Moyer wrote:
> Dan Williams writes:
>
There's a lot of special casing here, so you might consider adding
comments.
>>>
>>> Correct - maybe we should reconsider wrapper-izing this? :)
>>
>> Another option is just to skip dax_do_io() and this special
On 04/15/2016 01:06 PM, Tomasz Nowicki wrote:
> From the functionality point of view this series might be split into the
> following logic parts:
> 1. Necessary fixes as the preparation for using driver on ARM64.
> 2. New ECAM API and update for users of the pci-host-common API
> 3. Use new MCFG in
v2 -> v3: Improve naming in trigger. Absorb auxtrace_record__snapshot_started
and auxtrace_snapshot_err using trigger.
Cc: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: Adrian Hunter
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: pi3or...@163.com
W
With 'perf record --switch-output' without -a, record__synthesize() in
record__switch_output() won't generate tracking events because there's
no thread_map in evlist. Which causes newly created perf.data doesn't
contain map and comm information.
This patch creates a fake thread_map and directly ca
Allow 'perf record' to split its output into multiple files.
For example:
# ~/perf record -a --timestamp-filename --switch-output &
[1] 10763
# kill -s SIGUSR2 10763
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.2015122622314468 ]
# kill -s SIGUSR2 1076
Create a new class named 'trigger' to model the state of a trigger and
implement auxtrace_snapshot with it.
auxtrace_record__snapshot_started and auxtrace_snapshot_err are absorbed.
'trigger' defines 4 state transitioning functions ('on', 'released',
'toggle' and 'colddown') and 2 state query fun
Hi,
I am fingting with obscure pty bug in rhel6 which _might be_ explained
by some hangup/reopen races, and this motivated me to look at upstream
code which I can't understand too ;)
Lets look at tty_open(),
2112 tty = tty_open_current_tty(device, filp);
2113 if (!tty)
21
Tracking events describe kernel and threads. They are generated by
reading /proc/kallsyms, /proc/*/maps and /proc/*/task/* during
initialization of 'perf record', serialized into event sequences and put
at the head of 'perf.data'. In case of output switching, each output
file should contain those e
The cost of buildid cache processing is high: reading all events in
output perf.data, opening each elf file to read buildids then copying
them into ~/.debug directory. In switch output mode, these heavy works
block perf from receiving perf events for too long.
Enable no-buildid and no-buildid-cach
Bjorn Andersson wrote:
Your driver is a platform driver and it's being probed from DT. As such
all this is already taken care of for you, by the core.
The listing is for your reference to know why the dma-ranges property
would affect your device.
Ah, sorry. I misunderstood what you meant by "y
Without this patch, the last output doesn't have timestamp appended if
--timestamp-filename is not explicitly provided. For example:
# perf record -a --switch-output &
[1] 11224
# kill -s SIGUSR2 11224
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.201512262
On Fri, Apr 15, 2016 at 11:07:16AM -0700, Linus Torvalds wrote:
> On Fri, Apr 15, 2016 at 9:49 AM, Dave Jones wrote:
> > [] ? seq_vprintf+0x39/0x70
> > [] seq_vprintf+0x35/0x70
> > Code: 89 cd 49 01 fc 0f 82 18 03 00 00 48 89 7d b0 41 0f b6 07 0f 1f 84 00
> > 00 00 00 00 84 c0 74 43 48 8d
On Thu, 14 Apr 2016, Guenter Roeck wrote:
> Register with kernel restart handler instead of setting arm_pm_restart
> directly.
>
> Select a high priority of 192 to ensure that default restart handlers
> are replaced if Xen is running.
>
> Acked-by: Arnd Bergmann
> Reviewed-by: Wolfram Sang
> Re
Dan Williams writes:
> On Fri, Apr 15, 2016 at 11:06 AM, Jeff Moyer wrote:
>> Dan Williams writes:
>>
> There's a lot of special casing here, so you might consider adding
> comments.
Correct - maybe we should reconsider wrapper-izing this? :)
>>>
>>> Another option is just to
Byeoungwook Kim writes:
> rtl_*_delay() functions were reused same codes about addr variable.
> So i have converted to rtl_addr_delay() from code about addr variable.
>
> Signed-off-by: Byeoungwook Kim
> Reviewed-by: Julian Calaby
Doesn't apply:
Applying: rtlwifi: Fix reusable codes in core.c
Move the number of databases to the info structure.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6123.c | 6 +++---
drivers/net/dsa/mv88e6131.c | 8
drivers/net/dsa/mv88e6171.c | 8
drivers/net/dsa/mv88e6352.c | 12 ++--
drivers/net/dsa/mv88e6xxx.c | 19 +--
There is no point in having special case for the revision when probing a
switch model. The code gets cluttered with unnecessary defines, and
leads to errors when code such as mv88e6131_setup compares
PORT_SWITCH_ID_6131_B2 to ps->id which mask the revision.
Drop every revision definitions, add a p
Every driver assigns ps->ds even though it gets assigned in the shared
mv88e6xxx_setup_common function. Kill redundancy.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6123.c | 2 --
drivers/net/dsa/mv88e6131.c | 2 --
drivers/net/dsa/mv88e6171.c | 2 --
drivers/net/dsa/mv88e6352.c | 2 -
Add a new switch info structure which will be later extended to store
switch models static information, such as product number, name, number
of ports, number of databases, etc.
Merge the lookup function in the probing code, so that we avoid multiple
checking of the MII bus, as well a multiple ID r
We already have the product number and revision stored in the info
structure and the switch private state.
It is not necessary to clutter the header file with shifted product
number for devices that we don't even support yet. Remove them.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6
This patchset factorizes drastically the mv88e6xxx code by sharing a new
extendable info structure to store static data such as switch family,
product number, number of ports, number of databases and the name.
The next step is to add a "features" bitmap member to the info structure
in order to sim
Add an mv88e6xxx_family enum to the info structure for better family
indentification.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6123.c | 6 ++--
drivers/net/dsa/mv88e6131.c | 8 ++---
drivers/net/dsa/mv88e6171.c | 8 ++---
drivers/net/dsa/mv88e6352.c | 12
drivers/net/ds
2016-04-15 Christian König :
> Am 15.04.2016 um 10:02 schrieb Daniel Vetter:
> >On Thu, Apr 14, 2016 at 06:29:34PM -0700, Gustavo Padovan wrote:
> >>From: Gustavo Padovan
> >>
> >>struct fence_collection inherits from struct fence and carries a
> >>collection of fences that needs to be waited tog
Drop the ps->num_ports variable for a new member of the info structure.
This removes the need to assign it at setup time.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6123.c | 19 +++
drivers/net/dsa/mv88e6131.c | 26 +-
drivers/net/dsa/mv88e6171
2016-04-15 Daniel Vetter :
> On Fri, Apr 15, 2016 at 11:03 AM, Christian König
> wrote:
> > Might be that how amdgpu uses the fence context and sequence number is a bit
> > questionable, but this will completely break it.
>
> You mean it tries to qualesce fences in the same context down to just
On Thu, Apr 14, 2016 at 12:25 PM, Lorenzo Pieralisi
wrote:
> +void acpi_dma_configure(struct device *dev, enum dev_dma_attr attr)
> +{
> + struct iommu_ops *iommu;
> +
> + iommu = iort_iommu_configure(dev);
> +
> + /*
> +* Assume dma valid range starts at 0 and covers the
On 15/04/16 18:49, Laxman Dewangan wrote:
>
> On Friday 15 April 2016 11:14 PM, Jon Hunter wrote:
>> On 15/04/16 17:41, Laxman Dewangan wrote:
>>> On Friday 15 April 2016 09:15 PM, Jon Hunter wrote:
On 15/04/16 16:14, Laxman Dewangan wrote:
> I used pins as this is the property from pinc
split_huge_pages doesn't support get method at all, so the read permission
sounds confusing, change the permission to write only.
And, add "\n" to the output of set method to make it more readable.
Signed-off-by: Yang Shi
---
mm/huge_memory.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletio
On Fri, Apr 15, 2016 at 11:23 AM, Dave Jones wrote:
>
> To put my mind at rest though, am I wrong about that absent task_lock() stuff
> ?
So the task shouldn't be going away, because we are using the
proc_single_file_operations, which use proc_single_show(), which in
turn do a
task = ge
On Friday 15 April 2016 19:06:43 Tomasz Nowicki wrote:
> -MODULE_DEVICE_TABLE(of, thunder_pem_of_match);
> -
> -static int thunder_pem_probe(struct platform_device *pdev)
> +static int thunder_pem_init(struct device *dev, struct pci_config_window
> *cfg)
> {
> - struct device *dev = &pdev->
2016-04-15 Daniel Vetter :
> On Thu, Apr 14, 2016 at 06:29:37PM -0700, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > There is now a new property called FENCE_FD attached to every plane
> > state that receives the sync_file fd from userspace via the atomic commit
> > IOCTL.
> >
> > Th
On Fri, 15 Apr 2016, Michal Hocko wrote:
> On Fri 15-04-16 08:29:28, Mikulas Patocka wrote:
> >
> >
> > On Mon, 11 Apr 2016, Michal Hocko wrote:
> >
> > > From: Michal Hocko
> > >
> > > copy_params seems to be little bit confused about which allocation flags
> > > to use. It enforces GFP_NO
On Friday 15 April 2016 19:06:42 Tomasz Nowicki wrote:
> diff --git a/drivers/pci/ecam.h b/drivers/pci/ecam.h
> new file mode 100644
> index 000..34c0aba
> --- /dev/null
> +++ b/drivers/pci/ecam.h
>
You are including this file from device drivers and potentially from ACPI
code, so I think th
On Fri, 15 Apr 2016, Luis R. Rodriguez wrote:
> On Fri, Apr 15, 2016 at 3:06 AM, Julien Grall wrote:
> > On 14/04/16 21:56, Luis R. Rodriguez wrote:
> >> On Thu, Apr 14, 2016 at 03:56:53PM -0400, Konrad Rzeszutek Wilk wrote:
> >>> But to make that work you have to emulate EFI firmware in the
> >>>
On Fri, Apr 15, 2016 at 11:10:05AM -0700, Yang Shi wrote:
> split_huge_pages doesn't support get method at all, so the read permission
> sounds confusing, change the permission to write only.
>
> And, add "\n" to the output of set method to make it more readable.
>
> Signed-off-by: Yang Shi
Ack
On Friday 15 April 2016 22:13:55 Masahiro Yamada wrote:
> 2016-04-15 22:05 GMT+09:00 Mark Rutland :
> > On Fri, Apr 15, 2016 at 07:30:47PM +0900, Masahiro Yamada wrote:
> >> The 8-byte register located at 0x59801200 on this SoC is dedicated
> >> for waking up secondary CPUs. We can use it and save
* santosh shilimkar [160415 08:22]:
> On 4/15/2016 2:26 AM, Grygorii Strashko wrote:
> >
> >Santosh, Tony, do you want me to perform any additional actions regarding
> >this patch?
> >
> This patch should be run across family of SOCs to make
> sure wakeup works on all of those if not done already
On Saturday 16 April 2016 12:00 AM, Jon Hunter wrote:
On 15/04/16 18:49, Laxman Dewangan wrote:
On Friday 15 April 2016 11:14 PM, Jon Hunter wrote:
On 15/04/16 17:41, Laxman Dewangan wrote:
On Friday 15 April 2016 09:15 PM, Jon Hunter wrote:
On 15/04/16 16:14, Laxman Dewangan wrote:
I used
Hi David,
On 04/14/2016 03:00 PM, David Howells wrote:
> diff --git a/crypto/asymmetric_keys/signature.c
> b/crypto/asymmetric_keys/signature.c
> index 11b7ba170904..8ecbeda16b53 100644
> --- a/crypto/asymmetric_keys/signature.c
> +++ b/crypto/asymmetric_keys/signature.c
Since this file implement
On Fri, Apr 15, 2016 at 12:29 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> Since the boot_params can be found using the real_mode global variable,
>> there is
>> no need to pass around a pointer to it. This slightly simplifies the
>> choose_kernel_location function
On 04/15/2016 04:40 PM, James Bottomley wrote:
> On Fri, 2016-04-15 at 12:36 +0200, Denys Vlasenko wrote:
>> More info here:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70646
>
> This bug is under investigation, so I'd rather not alter code for a gcc
> bug until we know if we can supply option
On Fri, Apr 15, 2016 at 11:24 AM, Jeff Moyer wrote:
>> Moreover, we're going to do the full badblocks lookup anyway when we
>> call ->direct_access(). If we had that information earlier we can
>> avoid this fallback dance.
>
> None of the proposed approaches looks clean to me. I'll go along with
On 04/15/2016 05:50 AM, Juergen Gross wrote:
> On 15/04/16 12:40, mchri...@redhat.com wrote:
>> From: Mike Christie
>>
>> The last patch added a REQ_OP_FLUSH for request_fn drivers
>> and the next patch renames REQ_FLUSH to REQ_PREFLUSH which
>> will be used by file systems and make_request_fn dri
On 04/15, Bjorn Andersson wrote:
> On Thu 14 Apr 14:07 PDT 2016, John Stultz wrote:
>
> > Signed-off-by: John Stultz
> > ---
> > v2:
> > - Add wakeup-source entry as suggested by
> >Sudeep Holla
> >
> > arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts | 16 ++--
> > 1 file c
2016-04-15 Daniel Vetter :
> On Thu, Apr 14, 2016 at 06:29:38PM -0700, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Now a drm_pending_event can either send a real drm_event or signal a
> > fence, or both. It allow us to signal via fences when the buffer is
> > displayed on the screen
On Fri, Apr 15, 2016 at 12:47 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Baoquan He
>>
>> When processing the relocation table, the offset used to calculate the
>> relocation is an int. This is sufficient for calculating the physical
>> address of the relocs entry on 32-bit systems
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to per-cpu variables to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously. It uses the new per-cpu stats APIs provided by the
percpu_stats.h header file.
W
v3->v4:
- For patch 1, add the DIO_SKIP_DIO_COUNT flag to dax_do_io() calls
only to address issue raised by Dave Chinner.
v2->v3:
- Remove the percpu_stats helper functions and use percpu_counters
instead.
v1->v2:
- Remove percpu_stats_reset() which is not really needed in this
patchs
When performing direct I/O on DAX, the current ext4 code does not pass
in the DIO_SKIP_DIO_COUNT flag to dax_do_io() when inode_dio_begin()
has, in fact, been called. This causes dax_do_io() to invoke the
inode_dio_begin()/inode_dio_end() pair internally. This doubling of
inode_dio_begin()/inode_d
On Fri, 2016-04-15 at 20:56 +0200, Denys Vlasenko wrote:
> On 04/15/2016 04:40 PM, James Bottomley wrote:
> > On Fri, 2016-04-15 at 12:36 +0200, Denys Vlasenko wrote:
> > > More info here:
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70646
> >
> > This bug is under investigation, so I'd rath
2016-04-14 Rob Clark :
> On Thu, Apr 14, 2016 at 9:29 PM, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > This flag tells drm_atomic_ioctl that we want to get a per-crtc out-fence
> > fd back.
> >
> > Signed-off-by: Gustavo Padovan
> > ---
> > include/uapi/drm/drm_mode.h | 4 +++-
> >
The value stored in *cycle in xlog_crack_grant_head_val
in xfs_log_priv.h is compiler implementation dependent.
Does it matter?
static inline void
xlog_crack_grant_head_val(int64_t val, int *cycle, int *space)
{
*cycle = val >> 32;
*space = val & 0x;
}
On Fri, 2016-04-15 at 11:17 -0700, Dan Williams wrote:
> On Fri, Apr 15, 2016 at 11:06 AM, Jeff Moyer wrote:
> >
> > Dan Williams writes:
> >
> > > > > There's a lot of special casing here, so you might consider
> > > > > adding comments.
> > > > Correct - maybe we should reconsider wrapper-izi
On Fri, Apr 15, 2016 at 02:25:47PM -0400, Vivien Didelot wrote:
> Add an mv88e6xxx_family enum to the info structure for better family
> indentification.
>
> Signed-off-by: Vivien Didelot
> ---
> drivers/net/dsa/mv88e6123.c | 6 ++--
> drivers/net/dsa/mv88e6131.c | 8 ++---
> drivers/net/dsa/m
Dan Williams writes:
> On Fri, Apr 15, 2016 at 11:24 AM, Jeff Moyer wrote:
>>> Moreover, we're going to do the full badblocks lookup anyway when we
>>> call ->direct_access(). If we had that information earlier we can
>>> avoid this fallback dance.
>>
>> None of the proposed approaches looks cl
On Fri, Apr 15, 2016 at 1:07 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Baoquan He
>>
>> Currently CONFIG_RANDOMIZE_BASE_MAX_OFFSET is used to limit the maximum
>> offset for kernel randomization. This limit doesn't need to be a CONFIG
>> since it is tied completely to KERNEL_IMAGE
On Fri, Apr 15, 2016 at 1:12 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> Currently z_extract_offset is calculated in boot/compressed/mkpiggy.c.
>
> What is the high level meaning of z_extract_offset? I cannot tell without
> reading
> the code - and the point of cha
On Fri, Apr 15, 2016 at 02:25:46PM -0400, Vivien Didelot wrote:
> Add a new switch info structure which will be later extended to store
> switch models static information, such as product number, name, number
> of ports, number of databases, etc.
>
> Merge the lookup function in the probing code,
From: Mike Christie
The following patches separate the operation (write, read, discard,
etc) from the rq_flag_bits flags. This patch adds definitions for
request/bio operations, adds fields to the request/bio to set them, and
some temporary compat code so the kernel/modules can use either one. In
point, we abused them so much we just made cmd_flags
64 bits, so we could add more.
The following patches seperate the operation (read, write discard,
flush, etc) from cmd_flags/bi_rw.
This patchset was made against linux-next from today April 15
(git tag next-20160415).
I put a git tree here:
2016-04-15 Daniel Vetter :
> On Thu, Apr 14, 2016 at 06:29:41PM -0700, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Support DRM out-fences creating a sync_file with a fence for each crtc
> > update with the DRM_MODE_ATOMIC_OUT_FENCE flag.
> >
> > We then send an struct drm_out_fence
From: Mike Christie
To avoid confusion between REQ_OP_FLUSH, which is handled by
request_fn drivers, and upper layers requesting the block layer
perform a flush sequence along with possibly a WRITE, this patch
renames REQ_FLUSH to REQ_PREFLUSH.
Signed-off-by: Mike Christie
Reviewed-by: Christop
From: Mike Christie
This patch has f2fs use bio->bi_op for REQ_OPs and rq_flag_bits to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/f2fs/checkpoint.c| 10 ++
fs/f2fs/data.c | 33 --
From: Mike Christie
This patch converts the block layer merging code to use separate variables
for the operation and flags, and to check request->op for the REQ_OP.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
block/blk-core.c | 2 +-
bl
From: Mike Christie
This patch has dm use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
drivers/md/dm-bufio.c | 8 +++---
drivers/md/dm-crypt.c | 1 +
drivers/md/dm-io.
From: Mike Christie
This adds a REQ_OP_FLUSH operation that is sent to request_fn
based drivers by the block layer's flush code, instead of
sending requests with the request->cmd_flags REQ_FLUSH bit set.
For the following 3 flush related patches, I have not tested
every driver. I have only teste
From: Mike Christie
We no longer use REQ_WRITE. REQ_WRITE_SAME and REQ_DISCARD,
so this patch removes them.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
include/linux/blk_types.h | 21 ++---
include/linux/fs.h | 21 ++
On Fri, Apr 15, 2016 at 11:36:51AM +0100, Paul Burton wrote:
> asm/pgtable-bits.h is included in 2 assembly files and thus has to
> in either of the assembly files that include it.
That could do with rewording :-)
Otherwise
Reviewed-by: James Hogan
Cheers
James
>
> Remove the redundant inclus
From: Mike Christie
This patch has drbd use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Lars and Philip, I might have split this patch up a little weird.
The block layer has compat so you can set either bi_rw or bi_op.
This patch handles setting up the bio in drbd. I then converted
al
From: Mike Christie
The last patch added a REQ_OP_FLUSH for request_fn drivers
and the next patch renames REQ_FLUSH to REQ_PREFLUSH which
will be used by file systems and make_request_fn drivers so
they can send a write/flush combo.
This patch drops xen's use of REQ_FLUSH to track if it supports
From: Mike Christie
This patch has the target modules use bio->bi_op for REQ_OPs and
rq_flag_bits to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
Acked-by: Nicholas Bellinger
---
drivers/target/target_core_iblock.c | 30 +++
From: Mike Christie
This patch converts the elevator code to use separate variables
for the operation and flags, and to check request->op for the REQ_OP.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
block/blk-core.c | 2 +-
block/cfq-io
From: Mike Christie
This patch converts the is_sync helpers to use separate variables
for the operation and flags.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
block/blk-core.c | 6 +++---
block/blk-mq.c | 8
block/cfq-io
From: Mike Christie
bi_op only needed to be a int for temp compat reasons, so
this patch shrinks it to u8.
There is no need for bi_rw to be so large now, so that is
reduced to a unsigned int and bi_ioprio is just put in
its own field.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
From: Mike Christie
The request->op field is now always setup up with a REQ_OP.
This patch has the rq_data_dir helper convert the operation
to a WRITE or READ direction based on that.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
include/linux/b
From: Mike Christie
The bio and request structs now store the operation in
bio->bi_op/request->op. This patch has blktrace use that
field instead of bi_rw/cmd_flags.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
include/linux/blktrace_api.h |
On Fri, Apr 15, 2016 at 11:29:34AM -0700, Gustavo Padovan wrote:
> 2016-04-15 Daniel Vetter :
>
> > On Fri, Apr 15, 2016 at 11:03 AM, Christian König
> > wrote:
> > > Might be that how amdgpu uses the fence context and sequence number is a
> > > bit
> > > questionable, but this will completely b
From: Mike Christie
We no longer use the bio->bi_rw and request->cmd_flags field for REQ_OPs:
REQ_WRITE, REQ_DISCARD, REQ_WRITE_SAME, so this patch stops checking
for them in bi_rw/cmd_flags and also removes the related compat code.
v2:
1. Remove compat code in __get_request.
Signed-off-by: Mi
Hi,
On Fri, Apr 15, 2016 at 09:26:21AM +0200, Enric Balletbo i Serra wrote:
> The UCS1002-2 provides a USB port power switch for precise control of up
> to 2.5 amperes continuous current with over-current limit (OCL), dynamic
> thermal management, latch or auto-recovery (low test current) fault
>
From: Mike Christie
This patch modifies the blk mq request creation code to use
separate variables for the operation and flags, because in the
the next patches the struct request users will be converted like
was done for bios. request->op will be used for the REQ_OP and
request->cmd_flags for the
From: Mike Christie
The block layer will set the correct READ/WRITE operation flags/fields
when creating a request, so there is not need for drivers to set the
REQ_WRITE flag.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
drivers/ide/ide-cd_ioct
From: Mike Christie
This patch prepares *_get_request/*_put_request and freed_request,
to use separate variables for the operation and flags. In the
next patches the struct request users will be converted like
was done for bios. request->op will be used for the REQ_OP and
request->cmd_flags for t
From: Mike Christie
The bio and request operation and flags are going to be separate definitions,
so we cannot pass them in as a bitmap. This patch converts the blkg_rwstat
code and its caller, cfq, to pass in the values separately.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
R
From: Mike Christie
This patch has the block drivers use the request->op for REQ_OP
operations and cmd_flags for rq_flag_bits.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
drivers/block/loop.c | 6 +++---
drivers/block/mtip32xx/mt
From: Mike Christie
This has ll_rw_block users pass in the operation and flags separately,
so ll_rw_block can setup bio->bi_op and bio-bi_rw on the bio that
is submitted.
v2:
1. Fix for kbuild error in ll_rw_block comments.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed
On Fri, Apr 15, 2016 at 7:42 AM, Lasse Collin wrote:
> On 2016-04-14 Kees Cook wrote:
>> From: Yinghai Lu
>>
>> parse_elf is using a local memcpy to move sections to their final
>> running position. However, this memcpy only supports non-overlapping
>> arguments (or dest < src).
>
> The same copy
In virtualized environments, sometimes we need to limit the CPU
resources to a virtual machine(VM). For example in Xen, we use xl
sched-credit -d 1 -c 50 to limit the CPU resource of dom 1 as half of
one physical CPU core. If the VM CPU resource is capped, the process
inside the VM will have a vrun
From: Mike Christie
This patch has ocfs2 use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/ocfs2/cluster/heartbeat.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
dif
On Fri, Apr 15, 2016 at 1:31 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> Currently, the kernel run_size (size of code plus brk and bss) is
>> calculated via the shell script arch/x86/tools/calc_run_size.sh.
>> It gets the file offset and mem size of for the .bss and
From: Mike Christie
The bio bi_op and bi_rw is now setup, so there is no need
to pass around the rq_flag_bits bits too. btrfs users should should
access the bio.
v2:
1. Fix merge_bio issue where instead of removing rw/op argument
I passed it in again to the merge_bio related functions.
Signed-
From: Mike Christie
This patch has md use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
drivers/md/bitmap.c | 2 +-
drivers/md/dm-raid.c | 5 +++--
drivers/md/md.c | 11 +
From: Mike Christie
This patch has gfs2 use bio->bi_op for REQ_OPs and rq_flag_bits to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/gfs2/log.c| 8
fs/gfs2/lops.c | 12 +++-
fs/gfs2/lops.h |
On Fri, 2016-04-15 at 13:01 -0600, Toshi Kani wrote:
> On Fri, 2016-04-15 at 11:17 -0700, Dan Williams wrote:
> >
> > On Fri, Apr 15, 2016 at 11:06 AM, Jeff Moyer wrote:
> > >
> > > Dan Williams writes:
> > >
> > > > > > There's a lot of special casing here, so you might consider
> > > > > >
Hello, Paolo.
On Fri, Apr 15, 2016 at 06:17:55PM +0200, Paolo Valente wrote:
> > I don't think that is true with time based scheduling. If you
> > allocate 50% of time, it'll get close to 50% of IO time which
> > translates to bandwidth which is lower than 50% but still in the
> > ballpark.
>
>
From: Mike Christie
This patch has mpage.c use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/mpage.c | 41 +
1 file changed, 21 insertions(+), 20 d
From: Mike Christie
This patch has nilfs use bio->bi_op for REQ_OPs and rq_flag_bits
to bio->bi_rw.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/nilfs2/segbuf.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff
From: Mike Christie
We no longer pass in a bitmap of rq_flag_bits bits to __btrfs_map_block.
It will always be a REQ_OP, or the btrfs specific REQ_GET_READ_MIRRORS,
so this drops the bit tests.
Signed-off-by: Mike Christie
Reviewed-by: Christoph Hellwig
Reviewed-by: Hannes Reinecke
---
fs/bt
601 - 700 of 1033 matches
Mail list logo
