d
> leads to crashes.
>
> This changes back to only low memory being allocatable in the early
> stages, now using memblock allocation.
>
> Signed-off-by: Andreas Larsson
Acked-by: Mike Rapoport
> ---
> arch/sparc/mm/init_32.c | 3 +++
> 1 file changed, 3 insertions(+)
>
Hi Suzuki,.
On Tue, 2 Feb 2021 at 22:42, Suzuki K Poulose wrote:
>
> On 2/2/21 4:33 PM, Mike Leach wrote:
> > Hi,
> >
> > On Tue, 2 Feb 2021 at 09:42, Suzuki K Poulose
> > wrote:
> >>
> >> On 2/1/21 11:17 PM, Mathieu Poirier wrote:
> &g
Hi,
On Thu, 4 Feb 2021 at 11:08, Suzuki K Poulose wrote:
>
> On 2/4/21 4:09 AM, Leo Yan wrote:
> > Hi Mike,
> >
> > On Wed, Feb 03, 2021 at 05:39:54PM +, Mike Leach wrote:
> >
> > [...]
> >
> >>> +2.2) Tracing PID
> >>> +
On Wed, Feb 03, 2021 at 01:15:58PM +0100, Michal Hocko wrote:
> On Thu 21-01-21 14:27:18, Mike Rapoport wrote:
> > +static struct file *secretmem_file_create(unsigned long flags)
> > +{
> > + struct file *file = ERR_PTR(-ENOMEM);
> > + struct secretmem_ctx *ctx;
On Wed, Feb 03, 2021 at 01:09:30PM +0100, Michal Hocko wrote:
> On Tue 02-02-21 10:55:40, James Bottomley wrote:
> > On Tue, 2021-02-02 at 20:15 +0200, Mike Rapoport wrote:
> > > On Tue, Feb 02, 2021 at 03:34:29PM +0100, David Hildenbrand wrote:
> > > > On 02.0
On Wed, Feb 03, 2021 at 10:12:22AM +0100, Michal Hocko wrote:
> On Tue 02-02-21 21:10:40, Mike Rapoport wrote:
> >
> > Let me reiterate to make sure I don't misread your suggestion.
> >
> > If we make secretmem an opt-in feature with, e.g. kernel parameter, the
On 2/1/21 3:49 AM, Michal Hocko wrote:
> On Fri 29-01-21 10:46:15, Mike Kravetz wrote:
>> On 1/28/21 2:15 PM, Andrew Morton wrote:
>>> On Thu, 28 Jan 2021 14:00:29 -0800 Mike Kravetz
>>> wrote:
>>>>
>>>> Michal suggested that comments des
*/
> - if (rg->from > t)
> + if (rg->from >= t)
> break;
>
> /* Add an entry for last_accounted_offset -> rg->from, and
>
Changing any of this code makes me nervous. However, I agree with your
analysis. The change makes the code match the comment WRT the [from, to)
nature of regions.
Reviewed-by: Mike Kravetz
--
Mike Kravetz
On 2/2/21 11:42 PM, Muchun Song wrote:
> On Wed, Jan 20, 2021 at 9:33 AM Mike Kravetz wrote:
>>
>> Signed-off-by: Mike Kravetz
>
> Hi Mike,
>
> I found that you may forget to remove set_page_huge_active()
> from include/linux/hugetlb.h.
>
> diff --git a/inc
-
> 1 file changed, 27 insertions(+), 24 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 18f6ee317900..d2859c2aecc9 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
Thanks, that is a pretty straight forward change. A cleanup with no
functiona
spin_unlock(src_ptl);
> + spin_unlock(dst_ptl);
> + prealloc = alloc_huge_page(vma, addr,
> 0);
One quick que
- trace PID. Is this correct?
If so, then contextid, contextid1 and contextid2 have no effect except
in specific EL2 circumstances.
> +When the kernel is running at EL2 with VHE, if user wants to trace both the
> +PIDs for both host and gues
mutex);
Seems you're using this mutex to protect access to disk->interposer in
attach/detach. This is to prevent attach/detach races to same device?
Thankfully attach/detach isn't in the bio submission fast path but it'd
be helpful to document what this mutex is protecting).
A storm of attach or detach will all hit this global mutex though...
Mike
_queue_wait_timeout(struct request_queue *q,
>unsigned long timeout);
> +bool blk_mq_is_queue_frozen(struct request_queue *q);
>
> int blk_mq_map_queues(struct blk_mq_queue_map *qmap);
> void blk_mq_update_nr_hw_queues(struct blk_mq_tag_set *set, int
> nr_hw_queues);
> --
> 2.20.1
>
This needs to come before patch 2 (since patch 2 uses it).
Mike
Hallo
Mein Name ist George Mike. Ich bin von Beruf Rechtsanwalt. Ich möchte
Ihnen anbieten
der nächste Verwandte meines Klienten. Sie erben die Summe von (8,5
Millionen US-Dollar)
Dollar, die mein Kunde vor seinem Tod auf der Bank gelassen hat.
Mein Kunde ist ein Staatsbürger Ihres Landes, der
set_compound_order(page, 0);
> - page[1].compound_nr = 0;
I may be reading the code wrong, but set_compound_order(page, 0) will
set page[1].compound_nr to the value of 1. That is different than the
explicit setting to 0 in the existing code.
If that is correct, then you should say
| 2 ++
> 2 files changed, 6 insertions(+)
When you move this back into the "userfaultfd: add minor fault handling"
series, feel free to add:
Reviewed-by: Mike Kravetz
Thanks,
--
Mike Kravetz
,
For version 1, the reader will read the number of parameters in the
per CPU block. This allows the reader to process older or newer files
that may have different numbers of parameters than in use at the
time perf was built.
Signed-off-by: Mike Leach
Reviewed-by: Leo Yan
Tested-by: Leo Yan
hieu Poirier wrote:
> > Good morning,
> >
> > On Wed, Jan 27, 2021 at 05:53:50PM +, Mike Leach wrote:
> > > The current fixed metadata version format (version 0), means that adding
> > > metadata parameter items renders files from a previous version of perf
> &
b gigantic page' being <= 1 order, so this change
makes sense. Thanks,
Reviewed-by: Mike Kravetz
--
Mike Kravetz
>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>> index a3e4fa2c5e94..dac5db569ccb 100644
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -1219
On Tue, Feb 02, 2021 at 02:27:14PM +0100, Michal Hocko wrote:
> On Tue 02-02-21 14:48:57, Mike Rapoport wrote:
> > On Tue, Feb 02, 2021 at 10:35:05AM +0100, Michal Hocko wrote:
> > > On Mon 01-02-21 08:56:19, James Bottomley wrote:
> > >
> > > I h
vable? Timing attacks?
> > >
> > > I think the reason is simple: no direct map, no copying of memory.
> >
> > This is an implementation detail though and not something terribly hard
> > to add on top later on. I was more worried there would be really
> >
; 1)) {
> type = _type_encrypted;
> set_key = set_key_encrypted;
> -#endif
> } else {
> return -EINVAL;
> }
> --
> 2.30.0
>
I could be mistaken but the point of the previous way used to enable
this code was to not compile the code at all. How you have it, the
branch just isn't taken but the compiled code is left to bloat dm-crypt.
Why not leave this as is and follow same pattern in your next patch?
Mike
- we need to eliminate any
source that cannot reach it.
If not we need to find the relevant default sink for the source, which
might be a shared ETR, or per CPU TRBE / ETR, and the abstraction
logic ought to handle getting the captured data to the correct place.
If it doesn't then we are on shaky groun
nd when we pulled down the reset signal for the
Marvell 88E1512P PHY (because it requires at least 50ms after POR with
an active clock). Looking at the reset signal with a scope revealed a
short spike, point B in the artwork above.
Signed-off-by: Mike Looijmans
Reviewed-by: Andrew Lunn
---
Cha
regs". Please note that
"crash note regs" are a key piece of data used by crash dump debuggers
to provide a reliable backtrace of running processors.'
Secondary change pursuant to a5f526ec:
change master/slave to main/secondary
Signed-off-by: Georges Aureau
Signed
GBUS is way better than OOM at #PF
time.
And we can add some means to fail at mmap() time if the pools are running
low.
--
Sincerely yours,
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please consider the environment before printing this e-mail
component doesn't have any explicit connections (e.g,
> ETE) we could simply ignore the graph parsing.
>
> Cc: Mathieu Poirier
> Cc: Mike Leach
> Signed-off-by: Suzuki K Poulose
> Signed-off-by: Anshuman Khandual
> ---
> drivers/hwtracing/coresight/coresight-pl
olding
'big chunks' of memory for a specific purpose and dumping them when needed.
They were not doing this with hugetlb pages, but nothing would surprise me.
In this series, vmmap freeing is 'opt in' at boot time. I would expect
the use cases that want to opt in rarely if ever free/dissolve hugetlb
pages. But, I could be wrong.
--
Mike Kravetz
nto the same ifdef:
>
> #ifdef CONFIG_USERFAULTFD
> static inline int hugetlb_mcopy_atomic_pte(struct mm_struct *dst_mm,
> pte_t *dst_pte,
> struct vm_area_struct *dst_vma,
> unsigned long dst_addr,
> unsigned long src_addr,
> struct page **pagep)
> {
> BUG();
> return 0;
> }
> #endif /* CONFIG_USERFAULTFD */
>
> Let's also see whether Mike would have a preference on this.
>
No real preference. Just need to fix up the argument list in that
second definition.
--
Mike Kravetz
On Mon, Feb 01, 2021 at 03:32:33PM +0100, David Hildenbrand wrote:
> On 01.02.21 15:30, Mike Rapoport wrote:
> > >
> > > I'd suggest going through all zone ranges in free_area_init() first,
> > > dealing
> > > with zones that have "not section alig
ck to see if vma is sharable. Might be as
simple as !(vma->vm_flags & VM_MAYSHARE). I see a comment/question in
a later patch about only doing minor fault processing on shared mappings.
Code below looks fine, but it would be a wast to do all that for a vma
that could not be
-
> 2 files changed, 8 insertions(+), 8 deletions(-)
Reviewed-by: Mike Kravetz
--
Mike Kravetz
>
> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
> index 4508136c8376..f94a35296618 100644
> --- a/include/linux/hugetlb.h
> +++ b/include/linux/hugetlb.h
> @@ -96
turn false;
We are testing for uffd conditions that prevent sharing to determine if
huge_pmd_share should be called. Since we have the vma, perhaps we should
do the vma_sharable() test here as well? Or, perhaps delay all checks
until we are in huge_pmd_share and add uffd_disable_huge_pmd_share t
On 2/1/21 1:38 PM, Mike Kravetz wrote:
> On 1/28/21 3:42 PM, Axel Rasmussen wrote:
>> From: Peter Xu
>>
>> It is a preparation work to be able to behave differently in the per
>> architecture huge_pte_alloc() according to different VMA attributes.
>>
>>
d code, but would not be as efficient.
I prefer passing the vma argument as is done here.
Reviewed-by: Mike Kravetz
--
Mike Kravetz
e.kernel.org/lkml/127999c4-7d56-0c36-7f88-8e1a5c934...@collabora.com
--
Sincerely yours,
Mike.
On Mon, Feb 01, 2021 at 10:32:44AM +0100, David Hildenbrand wrote:
> On 30.01.21 23:10, Mike Rapoport wrote:
> > From: Mike Rapoport
> >
> > The physical memory on an x86 system starts at address 0, but this is not
> > always reflected in e820 map. For example, the
On Mon, Feb 01, 2021 at 05:39:58PM +0800, Baoquan He wrote:
> On 02/01/21 at 10:14am, David Hildenbrand wrote:
> > On 11.01.21 20:40, Mike Rapoport wrote:
> > > +
> > > +static void __init init_unavailable_mem(void)
> > > +{
> > > + int zone;
>
On Sun, Jan 31, 2021 at 01:49:27PM -0800, Linus Torvalds wrote:
> On Sun, Jan 31, 2021 at 12:04 AM Mike Rapoport wrote:
> >
> > >
> > > That's *particularly* true when the very line above it did a
> > > "memblock_reserve()" of the exact
0
>
> The issue was bisected to:
>
> commit cc9327f3b085ba5be5639a5ec3ce5b08a0f14a7c
> Author: Mike Rapoport
> Date: Thu Jan 28 07:42:40 2021 +
>
> mm: introduce memfd_secret system call to create "secret" memory areas
>
> bisection log:
On Sat, Jan 30, 2021 at 04:37:54PM -0800, Linus Torvalds wrote:
> On Sat, Jan 30, 2021 at 2:10 PM Mike Rapoport wrote:
> >
> > In either case, e820__memblock_setup() won't add the range 0x - 0x1000
> > to memblock.memory and later during memory map initialization t
From: Mike Rapoport
There could be struct pages that are not backed by actual physical
memory. This can happen when the actual memory bank is not a multiple
of SECTION_SIZE or when an architecture does not register memory holes
reserved by the firmware as memblock.memory.
Such pages
From: Mike Rapoport
Hi,
Commit 73a6e474cb37 ("mm: memmap_init: iterate over
memblock regions rather that check each PFN") exposed several issues with
the memory map initialization and these patches fix those issues.
Initially there were crashes during compaction that Qian Cai rep
From: Mike Rapoport
The physical memory on an x86 system starts at address 0, but this is not
always reflected in e820 map. For example, the BIOS can have e820 entries
like
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x1000-0x0009
Hallo
Mitt navn er George Mike. Jeg er advokat av yrke. Jeg ønsker å tilby deg
den pårørende til klienten min. Du vil arve summen av ($ 8,5 millioner)
dollar klienten min etterlot seg i banken før han døde.
Min klient er statsborger i landet ditt som døde i en bilulykke med sin kone
og eneste
On 1/28/21 2:15 PM, Andrew Morton wrote:
> On Thu, 28 Jan 2021 14:00:29 -0800 Mike Kravetz
> wrote:
>>
>> Michal suggested that comments describing synchronization be added for each
>> flag. Since I did 'one patch per flag', that would be an update to each
>> pa
On Thu, Jan 28, 2021 at 02:01:06PM +0100, Michal Hocko wrote:
> On Thu 28-01-21 11:22:59, Mike Rapoport wrote:
>
> > And hugetlb pools may be also depleted by anybody by calling
> > mmap(MAP_HUGETLB) and there is no any limiting knob for this, while
> > secretmem has
On Thu, Jan 28, 2021 at 07:28:57AM -0800, James Bottomley wrote:
> On Thu, 2021-01-28 at 14:01 +0100, Michal Hocko wrote:
> > On Thu 28-01-21 11:22:59, Mike Rapoport wrote:
> [...]
> > > One of the major pushbacks on the first RFC [1] of the concept was
> > > about t
t fails, we use part of the hugepage to
>remap.
I honestly am not sure about this. This would only happen for pages in
NORMAL. The only time using part of the huge page for vmemmap would help is
if we are trying to dissolve huge pages to free up memory for other uses.
> What's your opinion about this? Should we take this approach?
I think trying to solve all the issues that could happen as the result of
not being able to dissolve a hugetlb page has made this extremely complex.
I know this is something we need to address/solve. We do not want to add
more unexpected behavior in corner cases. However, I can not help but think
about similar issues today. For example, if a huge page is in use in
ZONE_MOVABLE or CMA there is no guarantee that it can be migrated today.
Correct? We may need to allocate another huge page for the target of the
migration, and there is no guarantee we can do that.
--
Mike Kravetz
On 1/28/21 1:37 PM, Andrew Morton wrote:
> On Thu, 28 Jan 2021 06:52:21 +0100 Oscar Salvador wrote:
>
>> On Wed, Jan 27, 2021 at 03:36:41PM -0800, Mike Kravetz wrote:
>>> Yes, this patch is somewhat optional. It should be a minor improvement
>>> in cases wh
+-
> 1 file changed, 28 insertions(+), 21 deletions(-)
Thanks for updating this.
Reviewed-by: Mike Kravetz
I think there still is an open general question about whether we can always
assume page structs are contiguous for really big pages. That is outside
of additional config and features by configfs
c) enhanced resource management for ETMv4 and checking features have sufficient
resources to be enabled.
d) ECT and CTI support for configuration and features.
Mike Leach (10):
coresight: syscfg: Initial coresight system configuration
coresight: syscfg: Add
currently registered devices. This allows
configuration loading after devices have been registered.
Signed-off-by: Mike Leach
---
.../hwtracing/coresight/coresight-config.h| 98 +
.../hwtracing/coresight/coresight-syscfg.c| 348 ++
.../hwtracing/coresight/coresight
Loaded coresight configurations are registered in the cs_etm\cs_config sub
directory. This extends the etm-perf code to handle these registrations,
and the cs_syscfg driver to perform the registration on load.
Signed-off-by: Mike Leach
---
.../hwtracing/coresight/coresight-config.h| 5
Adds documentation for the CoreSight System configuration manager.
Signed-off-by: Mike Leach
---
.../trace/coresight/coresight-config.rst | 244 ++
Documentation/trace/coresight/coresight.rst | 16 ++
2 files changed, 260 insertions(+)
create mode 100644 Documentation
generation on and off
using counters in the ETM.
A configuration called "autofdo" is also provided that uses the 'strobing'
feature and provides a couple of preset values, selectable on the perf
command line.
Signed-off-by: Mike Leach
---
drivers/hwtracing/coresight/Makefile
Configurations are first activated, then when any coresight device is
enabled, the active configurations are checked and any matching
one is enabled.
This patch provides the activation / enable API.
Signed-off-by: Mike Leach
---
.../hwtracing/coresight/coresight-config.h| 2
Add calls to activate the selected configuration as perf starts
and stops the tracing session.
Signed-off-by: Mike Leach
---
drivers/hwtracing/coresight/coresight-etm-perf.c | 14 +-
drivers/hwtracing/coresight/coresight-etm-perf.h | 2 ++
2 files changed, 15 insertions(+), 1
Adds configfs subsystem and attributes to the configuration manager
to enable the listing of loaded configurations and features.
The default values of feature parameters can be accessed and altered
from these attributes to affect all installed devices using the feature.
Signed-off-by: Mike Leach
Adds in handlers to allow the ETMv4 to use the complex configuration
support. Features and configurations can be loaded and selected in the
device.
Signed-off-by: Mike Leach
---
drivers/hwtracing/coresight/Makefile | 3 +-
.../hwtracing/coresight/coresight-etm4x-cfg.c | 184
Adds a set of generic support functions that allow devices to set and save
features values on the device, and enable and disable configurations.
Additional functions for other common operations including feature
reset.
Signed-off-by: Mike Leach
---
drivers/hwtracing/coresight/Makefile
configurations and features.
Signed-off-by: Mike Leach
---
drivers/hwtracing/coresight/Makefile | 2 +-
.../hwtracing/coresight/coresight-config.h| 167 +++
drivers/hwtracing/coresight/coresight-core.c | 12 +-
.../hwtracing/coresight/coresight-etm-perf.c | 2 +-
.../hwtracing
From: Mike Rapoport
Currently the first several pages are reserved both to avoid leaking their
contents on systems with L1TF and to avoid corrupting BIOS memory.
Merge the two memory reservations.
Signed-off-by: Mike Rapoport
Reviewed-by: David Hildenbrand
Acked-by: Borislav Petkov
From: Mike Rapoport
The early reservations of memory areas used by the firmware, bootloader,
kernel text and data are spread over setup_arch(). Moreover, some of them
happen *after* memblock allocations, e.g trim_platform_memory_ranges() and
trim_low_memory_range() are called after
From: Mike Rapoport
Hi,
David noticed that we do some of memblock_reserve() calls after allocations
are possible:
https://lore.kernel.org/lkml/6ba6bde3-1520-5cd0-f987-32d543f0b...@redhat.com
For now there is no actual problem because in top-down mode we allocate
from the end of the memory
ock_add calls (seen in the first first set of
> outputs) with overlapping address ranges that is done in bootmem_init
> also looks a bit worrying, but removing the second one does not affect
> this problem.
>
> --
> Best regards,
>
> Andreas Larsson
> Cobham Gaisler
--
Sincerely yours,
Mike.
On Thu, Jan 28, 2021 at 10:45:49AM +0800, Baoquan He wrote:
> On 01/27/21 at 08:26pm, Mike Rapoport wrote:
> > Hi Lukasz,
> >
> > On Wed, Jan 27, 2021 at 02:15:53PM +0100, Łukasz Majczak wrote:
> > > Hi Mike,
> > >
> > > I have sta
On Tue, Jan 26, 2021 at 01:08:23PM +0100, Michal Hocko wrote:
> On Tue 26-01-21 12:56:48, David Hildenbrand wrote:
> > On 26.01.21 12:46, Michal Hocko wrote:
> > > On Thu 21-01-21 14:27:19, Mike Rapoport wrote:
> > > > From: Mike Rapoport
> > > >
> &g
Hi Andrew,
Response below...
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please consider the environment
On 1/27/21 2:35 AM, Michal Hocko wrote:
> On Fri 22-01-21 11:52:29, Mike Kravetz wrote:
>> The HP_Migratable flag indicates a page is a candidate for migration.
>> Only set the flag if the page's hstate supports migration. This allows
>> the migration paths to detect non-mig
On 1/27/21 2:41 AM, Michal Hocko wrote:
> On Fri 22-01-21 11:52:31, Mike Kravetz wrote:
>> Use new hugetlb specific HPageFreed flag to replace the
>> PageHugeFreed interfaces.
>>
>> Signed-off-by: Mike Kravetz
>> Reviewed-by: Oscar Salvador
>> Reviewed
On 1/27/21 2:25 AM, Michal Hocko wrote:
> On Fri 22-01-21 11:52:28, Mike Kravetz wrote:
>> Use the new hugetlb page specific flag HPageMigratable to replace the
>> page_huge_active interfaces. By it's name, page_huge_active implied
>> that a huge page was on the
e and wait for
it to quiesce before mapping it to the requested port.
Add the code to drain unmapped queues during domain reset. This consists of
mapping a port to the queue, then calling the function to drain a mapped
queue.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Björn Töpel
> -Original Message-
> From: Greg KH
> Sent: Wednesday, January 27, 2021 9:04 AM
> To: Chen, Mike Ximing
> Cc: linux-kernel@vger.kernel.org; a...@arndb.de; Williams, Dan J
> ; pierre-louis.boss...@linux.intel.com
> Subject: Re: [PATCH v9 04/20] dlb: add device
the operation asynchronously.
To that end, the driver uses a workqueue that periodically checks whether
any outstanding operations can be completed. This workqueue function is
only scheduled when there is at least one outstanding map/unmap operation.
Signed-off-by: Gage Eads
Signed-off-by: Mike
Adds the "dynamic" map procedure and register operations. If a queue map
is requested after the domain is started, the driver must disable the
requested queue and wait for it to quiesce before mapping it to the
requested port.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
ap a
queue and then immediately requests to unmap it -- the driver will coalesce
or cancel outstanding operations.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Björn Töpel
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_resource.c | 433 +++-
1 fi
e "dynamic"
operation, when traffic is flowing in the device, will be added in a later
commit.)
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Björn Töpel
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_resource.c | 144 +++-
1 file cha
a single inode that is shared with other kernel
components -- calling unmap_mapping_range() on that shared inode would
likely break the kernel.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/Makefile
ns support rte_event_port_link(), rte_event_port_unlink()
and rte_event_port_unlinks_in_progress() functions of DPDK's eventdev
library.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Björn Töpel
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_ioctl.c| 9 +
driver
the DLB device to start load-balancing operations.
It corresponds to rte_event_dev_start() function in DPDK' eventdev library.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Björn Töpel
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_ioctl.c| 3 +
drivers/misc
ll mode". This (device-wide) mode is selected by the driver;
to determine the mode at run time, the driver provides an ioctl for
user-space software to query which mode the driver has configured. In this
way, the policy of which mode to use is decoupled from user-space software.
Signed-off-by: Ga
multiple iterations. This
process is finite since software cannot enqueue new events to the DLB's
(finite) on-device storage.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_hw_types.h | 46 +++
drivers/misc
they are re-assigned to a new
scheduling domain in the future and re-enabled.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_resource.c | 448 +++-
1 file changed, 443
On 1/27/21 2:20 AM, Michal Hocko wrote:
> [sorry for jumping in late]
>
> On Fri 22-01-21 11:52:27, Mike Kravetz wrote:
>> As hugetlbfs evolved, state information about hugetlb pages was added.
>> One 'convenient' way of doing this was to use available fields in tail
>>
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_hw_types.h | 27 ++
drivers/misc/dlb/dlb_ioctl.c| 63
drivers/misc/dlb/dlb_main.c | 2 +
drivers/misc/dlb/dlb_main.h | 17 +
drivers/misc/dlb/dlb_pf_ops.c | 36
Add a new entry in ioctl-number.rst
- Convert the ioctl handler into a switch statement
- Correct some instances of IOWR that should have been IOR
- Align macro blocks
- Don't break ioctl ABI when introducing new commands
- Remove indirect pointers from ioctl data structures
- Remove the get-
function (PF, as implemented here) or virtual
function/device (support to be added later).
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/Makefile | 1 +
drivers/misc/dlb/dlb_hw_types.h | 23
-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_main.c | 101 +-
drivers/misc/dlb/dlb_pf_ops.c | 8 +++
2 files changed, 108 insertions(+), 1 deletion(-)
diff --git a/drivers
).
Introduce dlb_bitmap_* functions, a thin convenience layer wrapping the
Linux bitmap interfaces, used by the bitmaps in the dlb hardware types.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/Makefile | 2
in the patch.
Add a DLB entry to the MAINTAINERS file.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
Documentation/misc-devices/dlb.rst | 259 +++
Documentation/misc-devices/index.rst | 1
Add operation to reset a domain's resource's software state when its
reference count reaches zero, and re-inserts those resources in their
respective available-resources linked lists, for use by future scheduling
domains.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed
) at that time. Support for these cases will be added in
subsequent commits.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_regs.h | 3527 ++-
drivers/misc/dlb/dlb_resource.c
-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
.../userspace-api/ioctl/ioctl-number.rst | 1 +
drivers/misc/dlb/Makefile | 2 +-
drivers/misc/dlb/dlb_bitmap.h | 32
drivers/misc/dlb
ded in subsequent commits.
Signed-off-by: Gage Eads
Signed-off-by: Mike Ximing Chen
Reviewed-by: Magnus Karlsson
Reviewed-by: Dan Williams
---
drivers/misc/dlb/dlb_bitmap.h | 74
drivers/misc/dlb/dlb_ioctl.c| 36 +-
drivers/misc/dlb/dlb_main.c | 68
drivers/misc/dlb/dlb_main.h |
Hi Mathieu,
On Wed, 27 Jan 2021 at 18:32, Mathieu Poirier
wrote:
>
> On Wed, Jan 27, 2021 at 05:53:50PM +, Mike Leach wrote:
> > The current fixed metadata version format (version 0), means that adding
> > metadata parameter items renders files from a previous version of p
Hi Lukasz,
On Wed, Jan 27, 2021 at 02:15:53PM +0100, Łukasz Majczak wrote:
> Hi Mike,
>
> I have started bisecting your patch and I have figured out that there
> might be something wrong with clamping - with comments out these lines
> it started to work.
> The full log (wi
block parameter.
3. Misc other fixes.
Signed-off-by: Mike Leach
---
tools/perf/arch/arm/util/cs-etm.c | 7 +-
tools/perf/util/cs-etm.c | 235 --
tools/perf/util/cs-etm.h | 30 +++-
3 files changed, 223 insertions(+), 49 deletions(-)
diff --git
801 - 900 of 19093 matches
Mail list logo
