From: Philipp Rossak
There is no need for pincontrol nodes when the pin is set to a GPIO
Signed-off-by: Philipp Rossak
---
This is Patch is a new version of the following patch:
https://patchwork.kernel.org/patch/9934835/
changes since version 1:
* vqmmc-supply was added again
* The pincontro
From: Markus Elfring
Date: Tue, 5 Sep 2017 22:30:22 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use common code in hdsp_get_iobox_version()
Use common error handling code in snd_hdspm_probe()
sound/pci/rme9652/hdsp.c | 26
On Tue, Sep 05, 2017 at 05:07:09PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 05, 2017 at 12:52:35PM -0700, Andi Kleen escreveu:
> > > > I'll check.
> > >
> > > Ok, I couldn't reproduce it anymore, after you check this, please let me
> > > know if I should pull that perf/intel-json-metri
From: Markus Elfring
Date: Tue, 5 Sep 2017 22:08:30 +0200
Add a jump target so that a bit of common code can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/pci/rme9652/hdsp.c | 26 +++-
On Fri, Sep 01, 2017 at 05:26:48PM +0800, Dennis Yang wrote:
> >On Mon, Aug 28, 2017 at 08:01:59PM +0800, Dennis Yang wrote:
> >> break_stripe_batch_list() did not preserve STRIPE_ON_UNPLUG_LIST which is
> >> set when a stripe_head gets queued to the stripe_head list maintained by
> >> raid5_plug_c
From: Markus Elfring
Date: Tue, 5 Sep 2017 22:22:21 +0200
Add a jump target so that a bit of exception handling can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/pci/rme9652/hdspm.c | 16
On 28/08/2017 18:42, Shuah Khan wrote:
> On 08/06/2017 05:23 PM, Mickaël Salaün wrote:
>> When a test process is not able to write to TH_LOG_STREAM, this step
>> mechanism enable to print the assert number which triggered the failure.
>> This can be enabled by setting _metadata->no_print to true
On Tue, Sep 5, 2017 at 5:21 PM, Tobias Klauser wrote:
> On 2017-09-05 at 17:11:50 +0200, Arnd Bergmann wrote:
>> On Tue, Sep 5, 2017 at 1:27 PM, Tobias Klauser wrote:
>> > Including linux/vmalloc.h in asm-generic/io.h isn't necessary since none
>> > of the definitions are used in the header itse
On Tue, 5 Sep 2017 19:15:50 +0100
Colin King wrote:
> From: Colin Ian King
>
> The u8 char array ret is not being initialized and elements outside
> the range start to end contain just garbage values from the stack.
> This results in a later scan of the array to read potentially
> uninitialize
On Tue, 5 Sep 2017 19:16:58 +0100
Colin King wrote:
> From: Colin Ian King
>
> The u8 char array ret is not being initialized and elements outside
> the range start to end contain just garbage values from the stack.
> This results in a later scan of the array to read potentially
> uninitialize
On Wed, Aug 30, 2017 at 2:58 AM, Abhisit Sangjan wrote:
> Hi Rob,
>
> On Sat, Aug 26, 2017 at 1:35 AM, Rob Herring wrote:
>>
>> On Tue, Aug 22, 2017 at 01:26:11PM +0700, s.abhi...@gmail.com wrote:
>> > From: Abhisit Sangjan
>> >
>> > TI LMP92001 Analog System Monitor and Controller
>> >
>> > 8-b
On Tue, Sep 5, 2017 at 8:16 PM, Geert Uytterhoeven
wrote:
> Correct location as of commit 2728b2d2e5be4b82 ("PM / core / docs:
> Convert sleep states API document to reST").
>
> Signed-off-by: Geert Uytterhoeven
> ---
> Note that the link was already broken before...
Yup, thanks, I'll queue this
On Thu, Aug 31, 2017 at 09:24:23AM +0200, Paolo VALENTE wrote:
>
> > Il giorno 15 gen 2017, alle ore 04:42, Shaohua Li ha scritto:
> >
> > Hi,
> >
> > cgroup still lacks a good iocontroller. CFQ works well for hard disk, but
> > not
> > much for SSD. This patch set try to add a conservative li
On Tue, Sep 05, 2017 at 05:58:54PM +0300, Dan Carpenter wrote:
> On Sun, Sep 03, 2017 at 10:12:46PM -0400, Brian Masney wrote:
> > On Sun, Sep 03, 2017 at 12:35:05PM +0100, Jonathan Cameron wrote:
> > > On Mon, 21 Aug 2017 13:11:03 +0300
> > > Dan Carpenter wrote:
> > >
> > > > The second part of
This patch fixes bavail and bfree finally.
longf_bfree;/* free blocks in fs */
longf_bavail; /* free blocks avail to non-superuser */
So, bfree represents all the reserved blocks, while bavail does the space only
visible to normal user.
Fix: 3e6d0b4d9c1c ("f2fs: fix incorrect f_bfr
From: Andi Kleen
It's not possible to run a package event and a per cpu event in
the same group. This is used by some of the power metrics.
They work correctly when not using a group.
Normally weak groups should handle that, but in this case EBADF
is returned instead of the normal EINVAL.
strac
Hi Nicolin,
On Tue, Sep 05, 2017 at 10:35:34AM +0200, Łukasz Majewski wrote:
And apparently, we shouldn't set bitclk to 66MHz either. Can
you help to find where this 66MHz comes from?
2. int asoc_simple_card_init_dai() @ simple-card-utils.c
Oh, I just searched in the simple-card.c but mis
Hi Fabio,
Hi Lukasz,
On Tue, Sep 5, 2017 at 5:35 AM, Łukasz Majewski wrote:
Note:
[*] - I could workaround this problem by setting:
system-clock-frequency = <0> in
dailink_master: cpu {
sound-dai = <&ssi2>;
};
On Mon, Sep 4, 2017 at 2:31 AM, Ingo Molnar wrote:
>
> Please pull the latest ... git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ...
Hmm. My laptop (XPS 13) doesn't resume any more. It suspends, but
doesn't come back from resume.
I immediately assumed it was the
Hello,
This mini-series further cleans up the SMP code for Actions Semi S500 SoC.
@David, can you please reply with an Acked-by for the second patch? Thanks!
Work branch for testing:
https://github.com/afaerber/linux/commits/bg96-next
Have a lot of fun!
Cheers,
Andreas
v1 -> v2:
* Prepended _
Commit 18cfd9429d8a82c49add8f3ca9d366599bfcac45 simplified the S500 SMP
code by removing a loop for pen_release in owl_secondary_boot().
Since then it is only calling owl_v7_invalidate_l1() before branching to
secondary_startup().
The owl_v7_invalidate_l1() assembler function is superfluous, too.
On Sep 5, 2017, at 3:06 PM, Jaegeuk Kim wrote:
>
> This patch fixes bavail and bfree finally.
>
> longf_bfree;/* free blocks in fs */
> longf_bavail; /* free blocks avail to non-superuser */
>
> So, bfree represents all the reserved blocks, while bavail does the space only
> visib
Replace an occurrence of virt_to_phys() with __pa_symbol() macro.
See 64fc2a947a9873700929ec0ef02b4654a04e0476 ("ARM: 8641/1: treewide:
Replace uses of virt_to_phys with __pa_symbol").
Fixes: 172067e0bc87 ("ARM: owl: Implement CPU enable-method for S500")
Reported-by: Florian Fainelli
Signed-off
From: Joe Perches
Date: Tue, 05 Sep 2017 13:01:18 -0700
> On Tue, 2017-09-05 at 21:45 +0200, Thomas Meyer wrote:
>> On Tue, Sep 05, 2017 at 11:50:44AM -0700, David Miller wrote:
>> > From: Thomas Meyer
>> > Date: Sun, 03 Sep 2017 14:19:31 +0200
>> >
>> > > Use ARRAY_SIZE macro, rather than expl
> On Saturday, September 10, 2016 at 2:00:06 PM UTC-4, Irina Tirdea wrote:
>
> Goodix devices have a configuration information register area that
> specifies various parameters for the device. ...
>
> Export a sysfs interface that would allow reading the configuration
> information. ...
>
> This
From: Jason Wang
Date: Mon, 4 Sep 2017 11:36:09 +0800
> Rename "generic_xdp" to "skb_xdp" to avoid confusing it with the
> generic XDP which will be done at netif_receive_skb().
>
> Cc: Daniel Borkmann
> Signed-off-by: Jason Wang
Applied.
From: Jason Wang
Date: Mon, 4 Sep 2017 11:36:08 +0800
> We reserve headroom unconditionally which could cause unnecessary
> stress on socket memory accounting because of increased trusesize. Fix
> this by only reserve extra headroom when XDP is set.
>
> Cc: Jakub Kicinski
> Signed-off-by: Jaso
Am 06.06.2017 um 02:54 schrieb Andreas Färber:
> Give the serial driver a fixed-clock as input for baudrate 115200.
>
> Signed-off-by: Andreas Färber
> ---
> v2 -> v3 -> v4: unchanged
>
> v2: new
>
> arch/arm64/boot/dts/actions/s900-bubblegum-96.dts | 7 +++
> 1 file changed, 7 inserti
From: Romain Perier
Date: Mon, 4 Sep 2017 10:41:36 +0200
> This code is no longer used, the logging function was changed by commit
> fbca164776e4 ("net: stmmac: Use the right logging function in
> stmmac_mdio_register").
> It was previously showing information about the type of the IRQ, if it's
> On Sep 5, 2017, at 2:17 PM, Linus Torvalds
> wrote:
>
>> On Mon, Sep 4, 2017 at 2:31 AM, Ingo Molnar wrote:
>>
>> Please pull the latest ... git tree from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ...
>
> Hmm. My laptop (XPS 13) doesn't resume any more. It suspen
Am 06.06.2017 um 02:54 schrieb Andreas Färber:
> Add a fixed-clock for baudrate 115200.
>
> Signed-off-by: Andreas Färber
> ---
> v2 -> v3 -> v4: unchanged
>
> v2: new
>
> arch/arm/boot/dts/s500-guitar-bb-rev-b.dts | 7 +++
> 1 file changed, 7 insertions(+)
Applied to v4.14/dt:
https
Hi Boris,
Thanks for detail review, I have incorporate the spell check
in my work flow and will be fixing all those spell check errors
innext rev.
On 09/05/2017 12:21 PM, Borislav Petkov wrote:
[...]
+3. KVM_SEV_LAUNCH_MEASURE
+
+Parameters (in): struct kvm_sev_launch_measure
+Returns: 0 o
* Linus Torvalds wrote:
> On Mon, Sep 4, 2017 at 2:31 AM, Ingo Molnar wrote:
> >
> > Please pull the latest ... git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ...
>
> Hmm. My laptop (XPS 13) doesn't resume any more. It suspends, but
> doesn't come back from
From: David Howells
Date: Mon, 04 Sep 2017 15:28:28 +0100
> When an RxRPC service packet comes in, the target connection is looked up
> by an rb-tree search under RCU and a read-locked seqlock; the seqlock retry
> check is, however, currently skipped if we got a match, but probably
> shouldn't be
On Tue, Sep 05, 2017 at 02:37:41PM -0700, Andy Lutomirski wrote:
> I can also imagine SME's very clever CR3 masking causing a problem.
So that mask should be 0 on an !SME system. One of the main goals of the
SME code was to have no effect when SME is disabled/not available.
--
Regards/Gruss,
From: Pavel Machek
Date: Mon, 4 Sep 2017 18:25:30 +0200
> Will gcc be able to compile code that uses these automatically? That
> does not sound easy to me. Can libc automatically use this in malloc()
> to prevent accessing freed data when buffers are overrun?
>
> Is this for benefit of JITs?
An
On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote:
>
> Does your laptop CPU have PCID support by any chance? The CPU coming
> out of resume with PCID disabled and us not properly re-enabling it
> might be a possible failure mode.
It does have pcid. It's a -7-6560U in the prev-gen XPS 13 (aka "935
From: Jason Wang
Date: Tue, 5 Sep 2017 09:22:05 +0800
> We check tx avail through vhost_enable_notify() in the past which is
> wrong since it only checks whether or not guest has filled more
> available buffer since last avail idx synchronization which was just
> done by vhost_vq_avail_empty() b
From: Håkon Bugge
Date: Tue, 5 Sep 2017 17:42:01 +0200
> The bits in m_flags in struct rds_message are used for a plurality of
> reasons, and from different contexts. To avoid any missing updates to
> m_flags, use the atomic set_bit() instead of the non-atomic equivalent.
>
> Signed-off-by: Håk
On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote:
>
> Hm, just as background, there are no regression reports I'm aware of
> against any of these trees, plus most of the dangerous commits have
> been in linux-next for at least two weeks - the majority of them even
> longer. The last 2-4 commits o
On Tue, Sep 05, 2017 at 03:44:12PM +0200, Michal Hocko wrote:
> Why is this an opt out rather than opt-in? IMHO the original oom logic
> should be preserved by default and specific workloads should opt in for
> the cgroup aware logic. Changing the global behavior depending on
> whether cgroup v2 in
Hi,
This is V2 of the inter-event tracing patchset.
There are too many changes to list in detail, most of them directly
addressing input from V1, but here are the major changes from V1
(thanks to everyone who reviewed V1 and thanks to both Vedang Patel
and Baohong Liu for their contributions and
From: Baohong Liu
Currently absolute timestamps are applied to both regular and max
buffers only for global trace. For instance trace, absolute
timestamps are applied only to regular buffer. But, regular and max
buffers can be swapped, for example, following a snapshot. So, for
instance trace, ba
The ring_buffer event can provide a timestamp that may be useful to
various triggers - pass it into the handlers for that purpose.
Signed-off-by: Tom Zanussi
---
include/linux/trace_events.h| 14 ++-
kernel/trace/trace.h| 9 +++
kernel/trace/trace_events_hist
Appending .usecs onto a common_timestamp field will cause the
timestamp value to be in microseconds instead of the default
nanoseconds. A typical latency histogram using usecs would look like
this:
# echo 'hist:keys=pid,prio:ts0=$common_timestamp.usecs ...
# echo 'hist:keys=next_pid:wakeup_
Future support for synthetic events requires hist_field 'type'
information, so add a field for that.
Also, make other hist_field attribute usage consistent (size,
is_signed, etc).
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 33 +
1 file chan
Add support for simple addition, subtraction, and unary expressions
(-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in
order to support a minimal set of useful inter-event calculations.
These operations are needed for calculating latencies between events
(timestamp1-timestamp0)
The tracepoint infrastructure assumes statically-defined tracepoints
and uses static_keys for tracepoint enablement. In order to define
tracepoints on the fly, we need to have a dynamic counterpart.
Add a 'dynamic' flag to struct tracepoint along with accompanying
logic for this purpose.
Signed-
Add an 'onmatch(matching.event).(param list)'
hist trigger action which is invoked with the set of variables or
event fields named in the 'param list'. The result is the generation
of a synthetic event that consists of the values contained in those
variables and/or fields at the time the invoking
Synthetic event generation requires the reservation of a second event
while the reservation of a previous event is still in progress. The
trace_recursive_lock() check in ring_buffer_lock_reserve() prevents
this however.
This sets up a special reserve pathway for this particular case,
leaving exis
The default clock if timestamps are used in a histogram is "global".
If timestamps aren't used, the clock is irrelevant.
Use the "clock=" param only if you want to override the default
"global" clock for a histogram with timestamps.
Signed-off-by: Tom Zanussi
---
Documentation/trace/events.txt
Allow tracing code outside of trace.c to access tracing_set_clock().
Some applications may require a particular clock in order to function
properly, such as latency calculations.
Also, add an accessor returning the current clock string.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 2 +
Users should be able to directly specify event fields in hist trigger
'actions' rather than being forced to explicitly create a variable for
that purpose.
Add support allowing fields to be used directly in actions, which
essentially does just that - creates 'invisible' variables for each
bare fiel
On Tue, 2017-09-05 at 09:25 -0500, Rob Herring wrote:
> > So in the meantime, I'm thinking adding some kind of runtime way
> > of disabling this default populate. Would you be ok with that ?
> >
> > Something like:
> >
> > bool arch_wants_of_platform_defaults(void)
> >
> > With a weak i
Lookups inflate the hitcount, making it essentially useless. Only
inserts and updates should really affect the hitcount anyway, so
explicitly filter lookups out.
Signed-off-by: Tom Zanussi
---
kernel/trace/tracing_map.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kerne
From: Vedang Patel
A duplicate in the tracing_map hash table is when 2 different entries
have the same key and, as a result, the key_hash. This is possible due
to a race condition in the algorithm. This race condition is inherent to
the algorithm and not a bug. This was fine because, until now, w
traceprobe_probes_write() and traceprobe_command() actually contain
nothing that ties them to kprobes - the code is generically useful for
similar types of parsing elsewhere, so separate it out and move it to
trace.c/trace.h.
Other than moving it, the only change is in naming:
traceprobe_probes_wr
Add background and details on inter-event hist triggers, including
hist variables, synthetic events, and actions.
Signed-off-by: Tom Zanussi
Signed-off-by: Baohong Liu
---
Documentation/trace/events.txt | 385 +
1 file changed, 385 insertions(+)
diff --g
Change the order event_mutex and trace_types_lock are taken, to avoid
circular dependencies and lockdep spew.
Changing the order shouldn't matter to any current code, but does to
anything that takes the event_mutex first and then trace_types_lock.
This is the case when calling tracing_set_clock fr
Synthetic events are user-defined events generated from hist trigger
variables saved from one or more other events.
To define a synthetic event, the user writes a simple specification
consisting of the name of the new event along with one or more
variables and their type(s), to the tracing/synthet
With the addition of variables and actions, it's become necessary to
provide more detailed error information to users about syntax errors.
Add a 'last error' facility accessible via the erroring event's 'hist'
file. Reading the hist file after an error will display more detailed
information about
Add support for alias=$somevar where alias can be used as
onmatch($alias).
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 61 ++--
1 file changed, 58 insertions(+), 3 deletions(-)
diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace
A common key to use in a histogram is the cpuid - add a new cpu
'synthetic' field for that purpose. This field is named cpu rather
than $cpu or $common_cpu because 'cpu' already exists as a special
filter field and it makes more sense to match that rather than add
another name for the same thing.
The existing code only allows for one space before and after the 'if'
specifying the filter for a hist trigger. Add code to make that more
permissive as far as whitespace goes.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 19 +++
1 file changed, 15 insertion
Add a hook for executing extra actions whenever a histogram entry is
added or updated.
The default 'action' when a hist entry is added to a histogram is to
update the set of values associated with it. Some applications may
want to perform additional actions at that point, such as generate
another
Add the necessary infrastructure to allow the variables defined on one
event to be referenced in another. This allows variables set by a
previous event to be referenced and used in expressions combining the
variable values saved by that previous event and the event fields of
the current event. Fo
Some accessor functions, such as for variable references, require
access to a corrsponding tracing_map_elt.
Add a tracing_map_elt param to the function signature and update the
accessor functions accordingly.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 91 +
Add an 'onmax(var).save(field,...)' hist trigger action which is
invoked whenever an event exceeds the current maximum.
The end result is that the trace event fields or variables specified
as the onmax.save() params will be saved if 'var' exceeds the current
maximum for that hist trigger entry. T
Named triggers must also have the same set of variables in order to be
considered compatible - update the trigger match test to account for
that.
The reason for this requirement is that named triggers with variables
are meant to allow one or more events to set the same variable.
Signed-off-by: To
Up until now, hist triggers only needed per-element support for saving
'comm' data, which was saved directly as a private data pointer.
In anticipation of the need to save other data besides 'comm', add a
new hist_elt_data struct for the purpose, and switch the current
'comm'-related code over to
Add support for saving the value of a current event's event field by
assigning it to a variable that can be read by a subsequent event.
The basic syntax for saving a variable is to simply prefix a unique
variable name not corresponding to any keyword along with an '=' sign
to any event field.
Bot
Allow hist_data access via hist_field. Some users of hist_fields
require or will require more access to the associated hist_data.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/kernel/trace/trace
This will make it easier to add variables, and makes the parsing code
cleaner regardless.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 56 +---
1 file changed, 35 insertions(+), 21 deletions(-)
diff --git a/kernel/trace/trace_events_hist.
In order to allow information to be passed between trace events, add
support for per-element variables to tracing_map. This provides a
means for histograms to associate a value or values with an entry when
it's saved or updated, and retrieved by a subsequent event occurrences.
Variables can be se
On Tue, Sep 05, 2017 at 04:39:14PM -0500, Brijesh Singh wrote:
> I was trying map with SEV firmware spec command names but I see your
> point and will call it "KVM_SEV_GET_GUEST_STATUS".
>
>
> > > +
> > > +enum {
> > > + /* guest state is not known */
> > > + SEV_STATE_INVALID = 0;
> >
> > not k
Add support for a timestamp event field. This is actually a 'pseudo-'
event field in that it behaves like it's part of the event record, but
is really part of the corresponding ring buffer event.
To make use of the timestamp field, users can specify
"$common_timestamp" as a field name for any his
RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can
gather was reserved for something like an absolute timestamp feature
for the ring buffer, if not a complete replacement of the current
time_delta scheme.
This code redefines RINGBUF_TYPE_TIME_STAMP to implement absolute time
stam
The current default for the number of subkeys in a compound key is 2,
which is too restrictive. Increase it to a more realistic value of 3.
Signed-off-by: Tom Zanussi
---
kernel/trace/tracing_map.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/tracing_map.h b/
In preparation for hist_fields that won't be strictly based on
trace_event_fields, add a new hist_field_name() accessor to allow that
flexibility and update associated users.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 67 +++-
1 file cha
Some events such as timestamps require access to a ring_buffer_event
struct; add a param so that hist field functions can access that.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 39 ---
1 file changed, 24 insertions(+), 15 deletions(-)
log2 as currently implemented applies only to u64 trace_event_field
derived fields, and assumes that anything it's applied to is a u64
field.
To prepare for synthetic fields like latencies, log2 should be
applicable to those as well, so take the opportunity now to fix the
current problems as well
Define a new function, tracing_set_time_stamp_abs(), which can be used
to enable or disable the use of absolute timestamps rather than time
deltas for a trace array.
This resets the buffer to prevent a mix of time deltas and absolute
timestamps.
Only the interface is added here; a subsequent patc
From: Vedang Patel
We now have the logic to detect and remove duplicates in the
tracing_map hash table. The code which merges duplicates in the
histogram is redundant now. So, modify this code just to detect
duplicates. The duplication detection code is still kept to ensure
that any rare race con
There are a small number of 'generic fields' (comm/COMM/cpu/CPU) that
are found by trace_find_event_field() but are only meant for
filtering. Specifically, they unlike normal fields, they have a size
of 0 and thus wreak havoc when used as a histogram key.
Exclude these (return -EINVAL) when used
On Tue, Sep 5, 2017 at 2:45 PM, Linus Torvalds
wrote:
>
> I have bisected a bit deeper, and the pcid code is definitely in that
> bisection window still. But are a fair number of other commits (about
> 160 right now)
Now down to 18.
And one of those 18 is commit 10af6235e0d3 ("x86/mm: Implement
On Tue, Sep 5, 2017 at 3:33 PM, Linus Torvalds
wrote:
> On Tue, Sep 5, 2017 at 2:45 PM, Linus Torvalds
> wrote:
>>
>> I have bisected a bit deeper, and the pcid code is definitely in that
>> bisection window still. But are a fair number of other commits (about
>> 160 right now)
>
> Now down to 18
Currently only the blocksize is checked, but we should really be calling
bdev_dax_supported() which also tests to make sure we can get a
struct dax_device and that the dax_direct_access() path is working.
This is the same check that we do for the "-o dax" mount option in
xfs_fs_fill_super().
Sign
The current code has an issue where the user can't reliably tell whether or
not DAX is being used to service page faults and I/O when the DAX mount
option is used. In this case each inode within the mounted filesystem
starts with S_DAX set due to the mount option, but it can be cleared if
someone
The following commit:
commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR
interface support")
added several defines related to extended attributes to ext4.h. They were
added within an #ifndef FS_IOC_FSGETXATTR block with the comment:
/* Until the uapi changes get merged for proj
This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
the complex conditional in ext4_set_inode_flags() and will soon be called
in multiple places.
Signed-off-by: Ross Zwisler
---
fs/ext4/ext4_jbd2.h | 15 +++
fs/ext4/inode.c | 4 +---
2 files changed, 16 i
Follow the lead of XFS and add a per-inode flag that allows the choice of
whether or not to use DAX to be made for individual files. As with XFS
this flag can also be set on a directory, in which case it will be
inherited by new inodes (both subdirectories and files) created within that
directory.
We prevent DAX from being used on inodes which are using ext4's built in
encryption via a check in ext4_should_use_dax(). We do have what appears
to be an unsafe transition of S_DAX in ext4_set_context(), though, where
S_DAX can get disabled without us doing a proper writeback + invalidate.
I act
Rework the error handling in ext4_change_inode_journal_flag() so that
multiple paths can re-use portions of the same cleanup code via gotos
instead of each path doing their own cleanup. This will benefit later
patches that add more paths to this function that must be unwound on error.
Signed-off-
If an inode has inline data it is currently prevented from using DAX by a
check in ext4_should_use_dax(). When the inode grows inline data via
ext4_create_inline_data() or removes its inline data via
ext4_destroy_inline_data_nolock(), the value of S_DAX can change.
Currently these changes are uns
The IOCTL path which switches the journaling mode for an inode is currently
unsafe because it doesn't properly do a writeback and invalidation on the
inode. In XFS, for example, safe transitions of S_DAX are handled by
xfs_ioctl_setattr_dax_invalidate() which locks out page faults and I/O,
does a
The original intent of this series was to add a per-inode DAX flag to ext4
so that it would be consistent with XFS. In my travels I found and fixed
several related issues in both ext4 and XFS.
I'm not fully happy with the ways that ext4 DAX interacts with conflicting
features (journaling, inline
On 09/05, Andreas Dilger wrote:
> On Sep 5, 2017, at 3:06 PM, Jaegeuk Kim wrote:
> >
> > This patch fixes bavail and bfree finally.
> >
> > longf_bfree;/* free blocks in fs */
> > longf_bavail; /* free blocks avail to non-superuser */
> >
> > So, bfree represents all the reserved
On Tue, Sep 05, 2017 at 11:13:40PM +0200, Łukasz Majewski wrote:
> They key point here is the asoc_simple_card_parse_clk() function
> from simple-card-utils.c
>
> Please look how the clock is assigned; It first checks for cpu
> clock, then for "system-clock-frequency" DTS node and _finally_
> loo
On Tue, 5 Sep 2017 22:05:00 +0300 Alexey Dobriyan wrote:
> Implement system call for bulk retrieveing of pids in binary form.
>
> Using /proc is slower than necessary: 3 syscalls + another 3 for each thread +
> converting with atoi().
>
> /proc may be not mounted especially in containers. Natur
On 9/4/2017 12:54 AM, Stephen Rothwell wrote:
> Just a reminder that this conflict still exists.
I suppose this was a message for Bjorn, right?
I looked at the change and it looked good to me.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc.
Q
601 - 700 of 819 matches
Mail list logo
