| Message ID | 158318762012.2216124.16408566404290491508.stgit@dwillia2-desk3.amr.corp.intel.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Manual definition of Soft Reserved memory devices | expand |
On 3/2/20 4:20 PM, Dan Williams wrote: > In support of detecting whether a resource might have been been claimed, > report the parent to the walk_iomem_res_desc() callback. For example, > the ACPI HMAT parser publishes "hmem" platform devices per target range. > However, if the HMAT is disabled / missing a fallback driver can attach > devices to the raw memory ranges as a fallback if it sees unclaimed / > orphan "Soft Reserved" resources in the resource tree. > > Otherwise, find_next_iomem_res() returns a resource with garbage data > from the stack allocation in __walk_iomem_res_desc() for the res->parent > field. Just wondering if we shouldn't just copy the complete resource struct and just override the start and end values? That way, if some code in the future wants to look at sibling or child values, another change isn't needed. Just a thought. Thanks, Tom > > Cc: Jason Gunthorpe <jgg@ziepe.ca> > Cc: Dave Hansen <dave.hansen@linux.intel.com> > Cc: Wei Yang <richardw.yang@linux.intel.com> > Cc: Tom Lendacky <thomas.lendacky@amd.com> > Signed-off-by: Dan Williams <dan.j.williams@intel.com> > --- > kernel/resource.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/kernel/resource.c b/kernel/resource.c > index 76036a41143b..6e22e312fd55 100644 > --- a/kernel/resource.c > +++ b/kernel/resource.c > @@ -386,6 +386,7 @@ static int find_next_iomem_res(resource_size_t start, resource_size_t end, > res->end = min(end, p->end); > res->flags = p->flags; > res->desc = p->desc; > + res->parent = p->parent; > } > > read_unlock(&resource_lock); >
On Thu, Mar 5, 2020 at 6:42 AM Tom Lendacky <thomas.lendacky@amd.com> wrote: > > On 3/2/20 4:20 PM, Dan Williams wrote: > > In support of detecting whether a resource might have been been claimed, > > report the parent to the walk_iomem_res_desc() callback. For example, > > the ACPI HMAT parser publishes "hmem" platform devices per target range. > > However, if the HMAT is disabled / missing a fallback driver can attach > > devices to the raw memory ranges as a fallback if it sees unclaimed / > > orphan "Soft Reserved" resources in the resource tree. > > > > Otherwise, find_next_iomem_res() returns a resource with garbage data > > from the stack allocation in __walk_iomem_res_desc() for the res->parent > > field. > > Just wondering if we shouldn't just copy the complete resource struct and > just override the start and end values? That way, if some code in the > future wants to look at sibling or child values, another change isn't needed. > > Just a thought. Thanks for taking a look. I think it's ok to come update this again if that need arises.
diff --git a/kernel/resource.c b/kernel/resource.c index 76036a41143b..6e22e312fd55 100644 --- a/kernel/resource.c +++ b/kernel/resource.c @@ -386,6 +386,7 @@ static int find_next_iomem_res(resource_size_t start, resource_size_t end, res->end = min(end, p->end); res->flags = p->flags; res->desc = p->desc; + res->parent = p->parent; } read_unlock(&resource_lock);
In support of detecting whether a resource might have been been claimed, report the parent to the walk_iomem_res_desc() callback. For example, the ACPI HMAT parser publishes "hmem" platform devices per target range. However, if the HMAT is disabled / missing a fallback driver can attach devices to the raw memory ranges as a fallback if it sees unclaimed / orphan "Soft Reserved" resources in the resource tree. Otherwise, find_next_iomem_res() returns a resource with garbage data from the stack allocation in __walk_iomem_res_desc() for the res->parent field. Cc: Jason Gunthorpe <jgg@ziepe.ca> Cc: Dave Hansen <dave.hansen@linux.intel.com> Cc: Wei Yang <richardw.yang@linux.intel.com> Cc: Tom Lendacky <thomas.lendacky@amd.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- kernel/resource.c | 1 + 1 file changed, 1 insertion(+)