On 10.03.2020 16:05, Paul Durrant wrote: >> -----Original Message----- >> From: Jan Beulich <jbeul...@suse.com> >> Sent: 10 March 2020 14:59 >> >> In reply to patch 6 I did suggest to >> have a separate list, but without taking these pages off >> d->page_list, > > How would that work without adding an extra page_list_entry into struct > page_info?
As said there, it'd be a singly linked list using a __pdx_t field just like there already is with "next_shadow", i.e. you'd add another union member "next_extra" or some such. Of course the list shouldn't grow too long, or else insertion and removal may become a bottleneck. Not sure how well this would fit Arm, though; maybe they wouldn't need this, but that depends on whether the list would be used for purposes beyond dumping. Jan >> such that here you would skip them in the main >> domain page dumping loop, but you would then traverse that second >> list and dump all of its elements, just like xenpage_list gets >> handled there. >> > > Well, that's what I'm trying to achieve, yes. > > Paul > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
