On Tue, Jun 02, 2020 at 02:55:52PM +0100, Emil Velikov wrote:
> On Mon, 1 Jun 2020 at 07:29, wrote:
> >
> > From: Sandor Yu
> >
> > - Extracted common fields from cdn_dp_device to a new cdns_mhdp_device
> > structure which will be used by two separate drivers later on.
> > - Moved some
On Tue, Jun 02, 2020 at 04:26:02PM -0700, Rajat Jain wrote:
> Currently, an external malicious PCI device can masquerade the VID:PID
> of faulty gfx devices, and thus apply iommu quirks to effectively
> disable the IOMMU restrictions for itself.
>
> Thus we need to ensure that the device we are
Hi Babu,
On 6/2/2020 3:12 PM, Babu Moger wrote:
>
>
>> -Original Message-
>> From: Reinette Chatre
>> Sent: Tuesday, June 2, 2020 4:51 PM
>> To: Moger, Babu ; fenghua...@intel.com;
>> t...@linutronix.de; mi...@redhat.com; b...@alien8.de; x...@kernel.org;
>> h...@zytor.com;
Hi Helen,
On Mon, Jun 01, 2020 at 01:36:59PM -0300, Helen Koike wrote:
> On 6/1/20 10:53 AM, Kaaira Gupta wrote:
> > Hi!
> >
> > Currently there is no method to know if the test image generated by vimc
> > is correct (except for comparing it with a known 'correct' image). So, I
> > wanted to
Florian
On 6/2/20 6:18 PM, Dan Murphy wrote:
Florian
On 6/2/20 6:13 PM, Florian Fainelli wrote:
On 6/2/2020 4:10 PM, Dan Murphy wrote:
Florian
On 6/2/20 5:33 PM, Florian Fainelli wrote:
On 6/2/2020 9:45 AM, Dan Murphy wrote:
Add RGMII internal delay configuration for Rx and Tx.
Currently, an external malicious PCI device can masquerade the VID:PID
of faulty gfx devices, and thus apply iommu quirks to effectively
disable the IOMMU restrictions for itself.
Thus we need to ensure that the device we are applying quirks to, is
indeed an internal trusted device.
On Tue, Jun 02, 2020 at 06:24:35PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The variable divider is being initialized with a value that is never read
> and it is being updated later with a new value. The initialization is
> redundant and can be removed.
Right. Thanks.
Reviewed-by:
On Tue, 2 Jun 2020, Stefan Hajnoczi wrote:
> Document the purpose of CAP_SETFCAP. For some reason this capability
> had no description while the others did.
>
> Signed-off-by: Stefan Hajnoczi
Thanks.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
Apologies for that slip up.
Reviewed-by: Evan Benn
On Wed, Jun 3, 2020 at 6:16 AM Julius Werner wrote:
>
> Reviewed-by: Julius Werner
On Wed, May 13, 2020 at 04:00:28PM +0200, Lars Povlsen wrote:
> This adds support for the Sparx5 SoC in the spi-dw-mchp SPI controller.
>
> Reviewed-by: Alexandre Belloni
> Signed-off-by: Lars Povlsen
> ---
> drivers/spi/spi-dw-mchp.c | 211 ++
> 1 file
On Tue, May 26, 2020 at 07:27:15AM -0700, Dave Hansen wrote:
> On 5/25/20 8:08 AM, Kirill A. Shutemov wrote:
> +if (not_addressable) {
> +pr_err("%lldGB of physical memory is not addressable in
> the paging mode\n",
> +
On Tue, Jun 02, 2020 at 10:23:53AM -0700, Darrick J. Wong wrote:
> On Tue, Apr 28, 2020 at 01:11:38PM -0700, Darrick J. Wong wrote:
> > On Mon, Apr 27, 2020 at 05:21:42PM -0700, ira.we...@intel.com wrote:
> > > From: Ira Weiny
> > >
...
> > > -out_unlock:
> > > - xfs_iunlock(ip,
On 6/2/2020 4:10 PM, Dan Murphy wrote:
> Florian
>
> On 6/2/20 5:33 PM, Florian Fainelli wrote:
>>
>> On 6/2/2020 9:45 AM, Dan Murphy wrote:
>>> Add RGMII internal delay configuration for Rx and Tx.
>>>
>>> Signed-off-by: Dan Murphy
>>> ---
>> [snip]
>>
>>> +
>>> enum {
>>>
On Wed, Jun 3, 2020 at 12:13 AM Tejun Heo wrote:
>
> Hello, Lai.
>
> On Tue, Jun 02, 2020 at 01:49:14PM +, Lai Jiangshan wrote:
> > +static void dec_nr_in_flight_flush_work(struct workqueue_struct *wq)
> > +{
> > + if (atomic_dec_and_test(>nr_flush_work))
>
> Do you think it'd make sense
Hi Daniel,
On 5/20/20 1:03 AM, Daniel W. S. Almeida wrote:
From: "Daniel W. S. Almeida"
Digital TV devices consist of several independent hardware components which
are controlled by different drivers.
Each media device is controlled by a group of cooperating drivers with the
bridge driver as
Florian
On 6/2/20 5:33 PM, Florian Fainelli wrote:
On 6/2/2020 9:45 AM, Dan Murphy wrote:
Add RGMII internal delay configuration for Rx and Tx.
Signed-off-by: Dan Murphy
---
[snip]
+
enum {
DP83869_PORT_MIRRORING_KEEP,
DP83869_PORT_MIRRORING_EN,
@@ -108,6 +113,8 @@ enum
On Mon, Jun 01, 2020 at 03:46:47PM -0400, Steven Rostedt wrote:
> On Mon, 1 Jun 2020 19:45:51 +0100
> Jules Irenge wrote:
>
> > Sparse reports warnings
> >
> > warning: context imbalance in ftrace_arch_code_modify_prepare()
> > - wrong count at exit
> > warning: context imbalance in
Hi all,
Today's linux-next merge of the drm-intel-fixes tree got a conflict in:
drivers/gpu/drm/i915/gt/intel_lrc.c
between commit:
f53ae29c0ea1 ("drm/i915/gt: Include a few tracek for timeslicing")
from Linus' tree and commit:
00febf644648 ("drm/i915/gt: Incorporate the virtual engine
On Wed, May 13, 2020 at 04:00:27PM +0200, Lars Povlsen wrote:
> This add DT bindings for the Sparx5 SPI driver.
This whole file can be easily merged in to the generic DW APB SSI DT
binding file. Just use "if: properties: compatible: const: ..." construction
to distinguish ocelot, jaguar, sparx5
On Wed, 3 Jun 2020 at 08:14, Linus Torvalds
wrote:
>
> On Mon, Jun 1, 2020 at 11:06 PM Dave Airlie wrote:
> >
> > I've pushed a merged by me tree here, which I think gets them all
> > correct, but please let me know if you think different.
> >
On Mon, Jun 1, 2020 at 10:55 AM Jens Axboe wrote:
>
> git://git.kernel.dk/linux-block.git for-5.8/io_uring-2020-06-01
I'm not sure why pr-tracker-bot didn't like your io_uring pull request.
It replied to your two other pull requests, but not to this one. I'm
not seeing any hugely fundamental
On Tue, 2020-06-02 at 12:14 -0700, Linus Torvalds wrote:
>
> On Tue, Jun 2, 2020 at 11:29 AM Thomas Gleixner wrote:
> >
> > It's trivial enough to fix. We have a static key already which is
> > telling us whether SMT scheduling is active.
>
> .. but should we do it here, in switch_mm() in the
Hi,
On Mon, Jun 1, 2020 at 9:20 AM Daniel Thompson
wrote:
>
> On Wed, May 27, 2020 at 05:02:27PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Tue, May 19, 2020 at 3:41 AM Daniel Thompson
> > wrote:
> > >
> > > On Thu, May 07, 2020 at 03:53:58PM -0700, Douglas Anderson wrote:
> > > > At times
On Wed, 29 Apr 2020 20:39:50 -0400
Yan Zhao wrote:
> On Wed, Apr 29, 2020 at 05:48:44PM +0800, Dr. David Alan Gilbert wrote:
>
> > > > > > > > > > > > > > An mdev type is meant to define a software
> > > > > > > > > > > > > > compatible interface, so in
> > > > > > > > > > > > > > the case of
On Fri, May 29, 2020 at 06:33:40PM +0200, Andrew Lunn wrote:
> Given the current code, you cannot. Now we understand the
> requirements, we can come up with some ideas how to do this properly.
Okay, I've been a little quiet because of sorting out the ARM tree
for merging with Linus (now done) and
02.06.2020 11:19, LABBE Corentin пишет:
...
>> Sounds like PLLE needs to be enabled for SATA, but ahci-tegra driver
>> doesn't do that.
>>
>> Could you please try this change:
>>
>> --- >8 ---
>> diff --git a/drivers/clk/tegra/clk-tegra124.c
>> b/drivers/clk/tegra/clk-tegra124.c
>> index
At times when I'm using kgdb I see a splat on my console about
suspicious RCU usage. I managed to come up with a case that could
reproduce this that looked like this:
WARNING: suspicious RCU usage
5.7.0-rc4+ #609 Not tainted
-
kernel/pid.c:395
On 6/1/20 6:38 AM, yu kuai wrote:
> commit e7bf90e5afe3 ("block/bio-integrity: fix a memory leak bug") add a
> kree() for 'buf' if bio_integrity_add_page() return '0'. However, the
> object will be freed in bio_integrity_free() since 'bio->bi_opf' and
> 'bio->bi_integrity' was set previousy in
Hi Rich,
On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker wrote:
>
> On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote:
> > Hi Rich,
> >
> > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker wrote:
> > >
> > > Could you reactivate linux-next pull from my arch/sh for-next branch?
> >
On 6/3/2020 12:37 AM, Jens Axboe wrote:
On 6/2/20 1:09 PM, Jason Gunthorpe wrote:
On Tue, Jun 02, 2020 at 01:02:55PM -0600, Jens Axboe wrote:
On 6/2/20 1:01 PM, Jason Gunthorpe wrote:
On Tue, Jun 02, 2020 at 11:37:26AM +0300, Max Gurtovoy wrote:
On 6/2/2020 5:56 AM, Stephen Rothwell wrote:
My Dear in the lord
My name is Mrs. Mina A. Brunel I am a Norway Citizen who is living in Burkina
Faso, I am married to Mr. Brunel Patrice, a politician who owns a small gold
company in Burkina Faso; He died of Leprosy and Radesyge, in the year February
2010, During his lifetime he
Add some test for get_count_order/long in test_bitops.c.
Signed-off-by: Wei Yang
---
v2: merge the test into test_bitops.c
---
lib/Kconfig.debug | 10 +-
lib/test_bitops.c | 40 ++--
2 files changed, 43 insertions(+), 7 deletions(-)
diff --git
Changeset 424037b77519 ("mm: smaps: Report arm64 guarded pages in smaps")
added a new parameter to a table. This causes Sphinx warnings,
because there's now an extra "-" at the wrong place:
/devel/v4l/docs/Documentation/filesystems/proc.rst:548: WARNING:
Malformed table.
Text in
Hi Jon,
It follows a couple of fixes for two tables that got broken, probably due to
some conflict between the ReST conversion patches and ungoing updates.
IMO, it would be nice to have those two applied during the merge window,
as they produce a too noisy output.
I have a few more fixes
As reported by Sphinx:
Documentation/filesystems/f2fs.rst:229: WARNING: Malformed table.
Text in column margin in table line 126.
==
background_gc=%s Turn on/off cleaning
Hi Yu!
I suggest a few minor wording tweaks to the commit message:
> commit e7bf90e5afe3 ("block/bio-integrity: fix a memory leak bug") add
s/add/added/
> a kree() for 'buf' if bio_integrity_add_page() return '0'. However,
> the
s/kree/kfree/
s/return/returns/
> object will be freed in
On Tue, Jun 02, 2020 at 03:31:11PM -0700, Guru Das Srinagesh wrote:
> Since the PWM framework is switching struct pwm_state.period's
> datatype to u64, prepare for this transition by using
> DIV_ROUND_UP_ULL to handle a 64-bit dividend.
>
> Signed-off-by: Guru Das Srinagesh
> ---
>
On 6/2/2020 9:45 AM, Dan Murphy wrote:
> Add RGMII internal delay configuration for Rx and Tx.
>
> Signed-off-by: Dan Murphy
> ---
[snip]
> +
> enum {
> DP83869_PORT_MIRRORING_KEEP,
> DP83869_PORT_MIRRORING_EN,
> @@ -108,6 +113,8 @@ enum {
> struct dp83869_private {
>
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using DIV_ROUND_UP_ULL to handle
a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Acked-by: Guenter Roeck
---
drivers/hwmon/pwm-fan.c | 2 +-
1 file changed, 1 insertion(+), 1
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using DIV64_U64_ROUND_CLOSEST to
handle a 64-bit divisor.
Cc: Daniel Thompson
Signed-off-by: Guru Das Srinagesh
---
drivers/pwm/pwm-clps711x.c | 2 +-
1 file changed, 1 insertion(+), 1
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using div64_u64() to handle a
64-bit divisor.
Also ensure that divide-by-zero (with fixed_rate as denominator) does
not happen with an explicit check with probe failure as a consequence.
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using DIV64_U64_ROUND_CLOSEST to
handle a 64-bit divisor.
Signed-off-by: Guru Das Srinagesh
Acked-by: Palmer Dabbelt
---
drivers/pwm/pwm-sifive.c | 2 +-
1 file changed, 1
Since the PWM framework is switching struct pwm_state.duty_cycle's
datatype to u64, prepare for this transition by using DIV_ROUND_UP_ULL
to handle a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Reviewed-by: Jani Nikula
Acked-by: Jani Nikula
---
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using nsecs_to_jiffies() which
does away with the need for a division operation.
Signed-off-by: Guru Das Srinagesh
Acked-by: Chen-Yu Tsai
---
drivers/pwm/pwm-sun4i.c | 2 +-
1 file
Because period and duty cycle are defined in the PWM framework structs as ints
with units of nanoseconds, the maximum time duration that can be set is limited
to ~2.147 seconds. Consequently, applications desiring to set greater time
periods via the PWM framework are not be able to do so - like,
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using DIV64_U64_ROUND_CLOSEST to
handle a 64-bit divisor.
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Signed-off-by: Guru Das
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using div_u64 to handle a 64-bit
dividend instead of a straight division operation.
Signed-off-by: Guru Das Srinagesh
Reviewed-by: Daniel Thompson
Acked-by: Lee Jones
---
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using DIV_ROUND_CLOSEST_ULL to
handle a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Acked-by: Sean Young
---
drivers/media/rc/ir-rx51.c | 3 ++-
1 file changed, 2
Since the PWM framework is switching struct pwm_state.period's
datatype to u64, prepare for this transition by using
DIV_ROUND_UP_ULL to handle a 64-bit dividend, and div64_u64 to handle a
64-bit divisor.
Also handle a possible overflow in the calculation of period_cycles when
both clk_rate and
Because period and duty cycle are defined as ints with units of
nanoseconds, the maximum time duration that can be set is limited to
~2.147 seconds. Change their definitions to u64 in the structs of the
PWM framework so that higher durations may be set.
Also use the right format specifiers in
Since the PWM framework is switching struct pwm_state.period's
datatype to u64, prepare for this transition by using
DIV_ROUND_UP_ULL to handle a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
---
drivers/pwm/pwm-imx27.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Aishwarya Ramakrishnan
Date: Tue, 2 Jun 2020 16:14:04 +0530
> As the "else if" and "else" branch body are identical the
> condition has no effect. So removing "else if" condition.
>
> Signed-off-by: Aishwarya Ramakrishnan
I'm not applying these patches, the conditional tests serve as
From: Piotr Stankiewicz
Date: Tue, 2 Jun 2020 11:21:05 +0200
> Seeing as there is shorthand available to use when asking for any type
> of interrupt, or any type of message signalled interrupt, leverage it.
>
> Signed-off-by: Piotr Stankiewicz
> Reviewed-by: Andy Shevchenko
Applied.
From: Piotr Stankiewicz
Date: Tue, 2 Jun 2020 11:21:11 +0200
> Seeing as there is shorthand available to use when asking for any type
> of interrupt, or any type of message signalled interrupt, leverage it.
>
> Signed-off-by: Piotr Stankiewicz
> Reviewed-by: Andy Shevchenko
Applied.
The pull request you sent on Tue, 2 Jun 2020 16:06:32 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2020-06-02
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/faa392181a0bd42c5478175cef601adeecdc91b6
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Mon, 1 Jun 2020 15:25:52 -0300:
> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus-hmm
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cfa3b8068b09f25037146bfd5eed041b78878bee
Thank you!
--
Deet-doot-dot, I am a
On Tue, Jun 02, 2020 at 10:36:11PM +0300, Dan Carpenter wrote:
> The callers don't expect *d_cdp to be set to an error pointer, they only
> check for NULL. This leads to a static checker warning:
>
> arch/x86/kernel/cpu/resctrl/rdtgroup.c:2648 __init_one_rdt_domain()
> warn: 'd_cdp'
On Mon, Jun 1, 2020 at 11:06 PM Dave Airlie wrote:
>
> I've pushed a merged by me tree here, which I think gets them all
> correct, but please let me know if you think different.
> https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-5.8-merged
Ok, I get the same result, except my resolution
Hi Sai,
On Tue, 2 Jun 2020 at 08:30, Sai Prakash Ranjan
wrote:
>
> Hi Mathieu,
>
> Thanks for taking your time for review.
>
> On 2020-06-02 02:58, Mathieu Poirier wrote:
> > Hi Sai,
> >
> > On top of the comments already privided by Mike, I have the following:
> >
> > On Mon, Jun 01, 2020 at
> -Original Message-
> From: Reinette Chatre
> Sent: Tuesday, June 2, 2020 4:51 PM
> To: Moger, Babu ; fenghua...@intel.com;
> t...@linutronix.de; mi...@redhat.com; b...@alien8.de; x...@kernel.org;
> h...@zytor.com; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86/resctrl: Fix
On Tue, Jun 02, 2020 at 04:42:03PM -0400, Michael S. Tsirkin wrote:
> On Tue, Jun 02, 2020 at 05:30:48PM +0100, Al Viro wrote:
> > On Tue, Jun 02, 2020 at 04:45:05AM -0400, Michael S. Tsirkin wrote:
> > > So vhost needs to poke at userspace *a lot* in a quick succession. It
> > > is thus
Hi Andrei,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on soc/for-next]
[also build test WARNING on arm/for-next kvmarm/next v5.7]
[cannot apply to arm64/for-next/core next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note
Hi Babu,
On 6/2/2020 10:33 AM, Babu Moger wrote:
>
>
> On 6/2/20 12:13 PM, Reinette Chatre wrote:
>> On 6/1/2020 4:00 PM, Babu Moger wrote:
>>> Memory bandwidth is calculated reading the monitoring counter
>>> at two intervals and calculating the delta. It is the software’s
>>> responsibility
On Tue, Jun 02, 2020 at 08:41:38PM +, David Laight wrote:
> In which case you need a 'user_access_begin' that takes the mm
> as an additional parameter.
What does any of that have to do with mm? Details, please.
On 6/2/2020 3:05 AM, Nicolas Saenz Julienne wrote:
> On Tue, 2020-05-05 at 18:13 +0200, Nicolas Saenz Julienne wrote:
>> On the Raspberry Pi 4, after a PCI reset, VL805's firmware may either be
>> loaded directly from an EEPROM or, if not present, by the SoC's
>> VideoCore. Inform VideoCore
On Tue, Jun 2, 2020 at 2:21 PM Linus Torvalds
wrote:
>
> I'm still working through the rest of the merge, so far that was the
> only one that made me go "Whaa?".
Hmm. I'm also ending up effectively reverting the drm commit
b28ad7deb2f2 ("drm/tidss: Use simple encoder") because commit
On Tue, Jun 2, 2020 at 5:41 PM Rob Herring wrote:
>
> On Tue, Jun 2, 2020 at 2:53 PM Jim Quinlan wrote:
> >
> > On Fri, May 29, 2020 at 1:46 PM Rob Herring wrote:
> > >
> > > On Tue, May 26, 2020 at 03:12:42PM -0400, Jim Quinlan wrote:
> > > > From: Jim Quinlan
> > > >
> > > > - Add compatible
As far as I know, this one's still unresolved. I can't see the bug from
code inspection, and we don't have a reproducer. If anyone else sees
this or has an idea what might be going wrong, I'd be interested.--b.
On Sun, May 17, 2020 at 11:59:12PM -0700, syzbot wrote:
> Hello,
>
> syzbot found
On Wed, Apr 29, 2020 at 12:08 PM Ian Rogers wrote:
>
> Counters may be being used for pinned or other events which inhibit the
> instruction counter in the test from being scheduled - time_enabled > 0
> but time_running == 0. This causes the test to fail with division by 0.
> Make time_running
Hi Babu,
On 6/1/2020 4:00 PM, Babu Moger wrote:
> Memory bandwidth is calculated reading the monitoring counter
> at two intervals and calculating the delta. It is the software’s
> responsibility to read the count often enough to avoid having
> the count roll over _twice_ between reads.
>
> The
On Tue, 2020-06-02 at 22:07 +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 02, 2020 at 12:54:16PM -0700, James Bottomley wrote:
[...]
> > I think the only way we can make the failure semantics consistent
> > is to have the kobject_init() ones (so kfree on failure). That
> > means for the add
I would like to ask the maintainers, Juergen, Boris, Konrad, whether you
have any more feedback before I send v2 of the series.
Cheers,
Stefano
On Wed, 20 May 2020, Stefano Stabellini wrote:
> Hi all,
>
> This series is a collection of fixes to get Linux running on the RPi4 as
> dom0.
>
>
Adding new metric test for frontend metric. It's stolen
from x86 pmu events.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/tests/parse-metric.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/tools/perf/tests/parse-metric.c
Adding new test that process metrics code and checks
the expected results. Starting with easy ipc metric.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/tests/Build | 1 +
tools/perf/tests/builtin-test.c | 4 +
tools/perf/tests/parse-metric.c | 145
Adding metricgroup__parse_groups_test function. It will
be used as test's interface to metric parsing in following
changes.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/metricgroup.c | 11 +++
tools/perf/util/metricgroup.h | 9 +
2 files changed, 20
Factoring out prepare_metric function so it can
be used in test interface coming in following
changes.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/stat-shadow.c | 53 ++-
1 file changed, 34 insertions(+), 19 deletions(-)
diff --git
Adding fake_pmu bool argument parse_events interface to
parse events and use fake pmu event in case pmu event
is parsed.
This way it's possible to parse events from PMUs which
are not present in the system. It's available only for
testing purposes coming in following changes, so all
the current
Adding the way to create pmu event without the actual
PMU being in place. This way we can test metrics defined
for any processors.
The interface is to define fake_pmu in struct parse_events_state
data. It will be used only in tests via special interface
function added in following changes.
For testing purposes we need to pass our own map of events
from parse_groups through metricgroup__add_metric.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/metricgroup.c | 23 +--
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git
Separating the generic part of check_parse_id function,
so it can be used in following changes for the new test.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/tests/pmu-events.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git
Allow to pass fake_pmu in parse_groups function
so it can be used in parse_events call.
It's set true by metricgroup__parse_groups_test
function.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/metricgroup.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
The test goes through all metrics compiled for arch
within pmu events and try to parse them.
This test is different from 'test_parsing' in that
we go through all the events in the current arch,
not just one defined for current CPU model. Using
'fake_pmu' to parse events which do not have PMUs
On 6/2/20 11:18 AM, Randy Dunlap wrote:
> On 6/2/20 3:37 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: The merge window has opened, so please do *not* add v5.9 material
>> to your linux-next included branches until after v5.8-rc1 has been
>> released.
>>
>> Changes since 20200529:
>>
> on
Adding test_generic_metric that prepares and runs given metric
over the data from struct runtime_stat object.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/stat-shadow.c | 14 ++
tools/perf/util/stat.h| 3 +++
2 files changed, 17 insertions(+)
diff
We don't release metric_events rblist, add the missing
delete hook and call the release before leaving cmd_stat.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/builtin-stat.c | 1 +
tools/perf/util/metricgroup.c | 19 +++
tools/perf/util/metricgroup.h | 1 +
Factor out the parse_groups function, it will be used
for new test interface coming in following changes.
Acked-by: Ian Rogers
Signed-off-by: Jiri Olsa
---
tools/perf/util/metricgroup.c | 22 --
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git
hi,
changes for using metric result in another metric seem
to change lot of core metric code, so it's better we
have some more tests before we do that.
v3 changes:
- few typo fixes [Ian]
- move struct parse_events_error one level up in check_parse_id [Ian]
- added Ian's acks
v2 changes:
On Tue, Jun 2, 2020 at 2:04 PM Pavel Machek wrote:
>
> On Wed 2020-05-27 08:35:06, Rob Herring wrote:
> > On Wed, May 27, 2020 at 7:39 AM Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > Thanks for reviews!
> > >
> > > > > +additionalProperties: false
> > > > > +...
> > > > > diff --git
On Wed, May 20, 2020 at 07:10:06PM -0500, Suman Anna wrote:
> The resets for the DSP processors on K3 SoCs are managed through the
> Power and Sleep Controller (PSC) module. Each DSP typically has two
> resets - a global module reset for powering on the device, and a local
> reset that affects
On Tue, Jun 2, 2020 at 2:53 PM Jim Quinlan wrote:
>
> On Fri, May 29, 2020 at 1:46 PM Rob Herring wrote:
> >
> > On Tue, May 26, 2020 at 03:12:42PM -0400, Jim Quinlan wrote:
> > > From: Jim Quinlan
> > >
> > > - Add compatible strings for three more Broadcom STB chips: 7278, 7216,
> > > 7211
On 6/2/20 1:09 PM, Jason Gunthorpe wrote:
> On Tue, Jun 02, 2020 at 01:02:55PM -0600, Jens Axboe wrote:
>> On 6/2/20 1:01 PM, Jason Gunthorpe wrote:
>>> On Tue, Jun 02, 2020 at 11:37:26AM +0300, Max Gurtovoy wrote:
On 6/2/2020 5:56 AM, Stephen Rothwell wrote:
> Hi all,
Hi,
linux/kernel.h is a uapi header that does almost nothing but define
some internal-use alignment macros and -- oddly -- include
linux/sysinfo.h to provide a definition of struct sysinfo. It's
included only from 6 places in the kernel uapi headers:
include/uapi/linux/lightnvm.h
Hi KP,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
[cannot apply to bpf/master linus/master linux/master v5.7 next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use
The current codebase makes use of one-element arrays in the following
form:
struct something {
int length;
u8 data[1];
};
struct something *instance;
instance = kmalloc(sizeof(*instance) + size, GFP_KERNEL);
instance->length = size;
memcpy(instance->data, source, size);
but the
Hi,
On Fri, May 29, 2020 at 4:27 AM Sumit Garg wrote:
>
> In kgdb context, calling console handlers aren't safe due to locks used
> in those handlers which could in turn lead to a deadlock. Although, using
> oops_in_progress increases the chance to bypass locks in most console
> handlers but it
Hi,
On Fri, May 29, 2020 at 4:27 AM Sumit Garg wrote:
>
> While rounding up CPUs via NMIs, its possible that a rounded up CPU
> maybe holding a console port lock leading to kgdb master CPU stuck in
> a deadlock during invocation of console write operations. A similar
> deadlock could also be
Hi,
On Fri, May 29, 2020 at 4:27 AM Sumit Garg wrote:
>
> Check if a console is enabled prior to invoking corresponding write
> handler.
>
> Suggested-by: Sergey Senozhatsky
> Signed-off-by: Sumit Garg
> Reviewed-by: Daniel Thompson
> ---
> kernel/debug/kdb/kdb_io.c | 2 ++
> 1 file changed,
Hi,
On Fri, May 29, 2020 at 4:27 AM Sumit Garg wrote:
>
> Re-factor kdb_printf() message write code in order to avoid duplication
> of code and thereby increase readability.
>
> Signed-off-by: Sumit Garg
> ---
> kernel/debug/kdb/kdb_io.c | 61
> +--
On Tue, Jun 02, 2020 at 08:13:59PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.226 release.
> There are 55 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Tue, Jun 2, 2020 at 2:21 PM Linus Torvalds
wrote:
>
> Hmm. Some of them are due to your previous mis-merges.
>
> Your commit 937eea297e26 ("Merge tag 'amd-drm-next-5.8-2020-04-24' of
> git://people.freedesktop.org/~agd5f/linux into drm-next") seems to
> have mis-merged the CONFIG_DEBUG_FS
201 - 300 of 1198 matches
Mail list logo
