From: "Jan Beulich" <JBeulich@suse.com> To: Julien Grall <julien.grall@arm.com>, Stefano Stabellini <sstabellini@kernel.org> Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Stefano Stabellini <stefanos@xilinx.com>, nd@arm.com, 206497@studenti.unimore.it, xen-devel <xen-devel@lists.xenproject.org> Subject: Re: [PATCH] xen/arm: skip first page when RAM starts at 0x0 Date: Fri, 26 Apr 2019 03:12:44 -0600 [thread overview] Message-ID: <5CC2CB8C02000078002295AA@prv1-mh.provo.novell.com> (raw) In-Reply-To: <981e7b3f-464b-d37c-e03e-22408ae65f85@arm.com> >>> On 25.04.19 at 23:27, <Julien.Grall@arm.com> wrote: > On 25/04/2019 18:51, Stefano Stabellini wrote: >> Xen assumes that RAM starts at addresses greater than 0x0 in a few >> places. The PDX code is one of them but there are more. > > A bit more context in the commit message would have been useful. Imagine > if we have to look at the commit message it in 2 years time. > >> >> For now, skip the first page in memory when the start addess is 0x0. >> >> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com> Isn't this in response to a bug report / completely different code change from someone at DornerWorks? In which case shouldn't there be a Reported-by? > For a first we need to gather feedback from contributors that know a bit > more of the code that may be affected. AFAICT, there are only two pieces > where we hand over memory to common code: > - PDX: The problem is passing 0 to pdx_init_mask() will result to a > ~0 mask defeating the compression later on. On x86 the function gets called only for memory blocks above 4Gb. Question is whether on Arm you also have some ad hoc boundary below which there's no point to look for bits to compact. If not I wonder why you call the function at all; at the very least (as you seem to imply) it shouldn't be called when bootinfo.mem.bank[0].start is zero. > - Buddy allocator: Jan has been suggesting to stick a check in > init_xenheap_pages(). This would go the other ugliness existing to deal > with the buddy allocator. And this would then also take care of future architectures Xen may get ported to. (No idea what other ugliness you refer to.) Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com> To: "Julien Grall" <julien.grall@arm.com>, "Stefano Stabellini" <sstabellini@kernel.org> Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Stefano Stabellini <stefanos@xilinx.com>, nd@arm.com, 206497@studenti.unimore.it, xen-devel <xen-devel@lists.xenproject.org> Subject: Re: [Xen-devel] [PATCH] xen/arm: skip first page when RAM starts at 0x0 Date: Fri, 26 Apr 2019 03:12:44 -0600 [thread overview] Message-ID: <5CC2CB8C02000078002295AA@prv1-mh.provo.novell.com> (raw) Message-ID: <20190426091244.wjJ8eYd4WL3Ily00I-KdvNM6hK_dTs7GwpWFS_F77Bo@z> (raw) In-Reply-To: <981e7b3f-464b-d37c-e03e-22408ae65f85@arm.com> >>> On 25.04.19 at 23:27, <Julien.Grall@arm.com> wrote: > On 25/04/2019 18:51, Stefano Stabellini wrote: >> Xen assumes that RAM starts at addresses greater than 0x0 in a few >> places. The PDX code is one of them but there are more. > > A bit more context in the commit message would have been useful. Imagine > if we have to look at the commit message it in 2 years time. > >> >> For now, skip the first page in memory when the start addess is 0x0. >> >> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com> Isn't this in response to a bug report / completely different code change from someone at DornerWorks? In which case shouldn't there be a Reported-by? > For a first we need to gather feedback from contributors that know a bit > more of the code that may be affected. AFAICT, there are only two pieces > where we hand over memory to common code: > - PDX: The problem is passing 0 to pdx_init_mask() will result to a > ~0 mask defeating the compression later on. On x86 the function gets called only for memory blocks above 4Gb. Question is whether on Arm you also have some ad hoc boundary below which there's no point to look for bits to compact. If not I wonder why you call the function at all; at the very least (as you seem to imply) it shouldn't be called when bootinfo.mem.bank[0].start is zero. > - Buddy allocator: Jan has been suggesting to stick a check in > init_xenheap_pages(). This would go the other ugliness existing to deal > with the buddy allocator. And this would then also take care of future architectures Xen may get ported to. (No idea what other ugliness you refer to.) Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-26 9:12 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-25 17:51 [PATCH] xen/arm: skip first page when RAM starts at 0x0 Stefano Stabellini 2019-04-25 17:51 ` [Xen-devel] " Stefano Stabellini 2019-04-25 21:27 ` Julien Grall 2019-04-25 21:27 ` [Xen-devel] " Julien Grall 2019-04-26 9:12 ` Jan Beulich [this message] 2019-04-26 9:12 ` Jan Beulich 2019-04-26 9:19 ` Julien Grall 2019-04-26 9:19 ` [Xen-devel] " Julien Grall 2019-04-26 9:42 ` Jan Beulich 2019-04-26 9:42 ` [Xen-devel] " Jan Beulich 2019-04-26 15:38 ` Julien Grall 2019-04-26 15:38 ` [Xen-devel] " Julien Grall 2019-04-26 15:48 ` Jan Beulich 2019-04-26 15:48 ` [Xen-devel] " Jan Beulich 2019-04-26 21:31 ` Julien Grall 2019-04-26 21:31 ` [Xen-devel] " Julien Grall 2019-04-26 23:47 ` Stefano Stabellini 2019-04-26 23:47 ` [Xen-devel] " Stefano Stabellini 2019-04-27 19:43 ` Julien Grall 2019-04-27 19:43 ` [Xen-devel] " Julien Grall 2019-04-29 7:15 ` Jan Beulich 2019-04-29 7:15 ` [Xen-devel] " Jan Beulich 2019-04-29 15:54 ` Julien Grall 2019-04-29 15:54 ` [Xen-devel] " Julien Grall 2019-04-29 16:07 ` Jan Beulich 2019-04-29 16:07 ` [Xen-devel] " Jan Beulich 2019-04-29 17:51 ` Stefano Stabellini 2019-04-29 17:51 ` [Xen-devel] " Stefano Stabellini 2019-05-01 22:44 ` Stefano Stabellini 2019-05-01 22:44 ` [Xen-devel] " Stefano Stabellini 2019-05-02 7:30 ` Jan Beulich 2019-05-02 7:30 ` [Xen-devel] " Jan Beulich 2019-05-02 9:02 ` Julien Grall 2019-05-02 9:02 ` [Xen-devel] " Julien Grall 2019-05-02 9:20 ` Jan Beulich 2019-05-02 9:20 ` [Xen-devel] " Jan Beulich 2019-05-02 22:25 ` Stefano Stabellini 2019-05-02 22:25 ` [Xen-devel] " Stefano Stabellini 2019-05-03 7:26 ` Jan Beulich 2019-05-03 7:26 ` [Xen-devel] " Jan Beulich 2019-05-03 20:16 ` Stefano Stabellini 2019-05-03 20:16 ` [Xen-devel] " Stefano Stabellini 2019-04-29 7:07 ` Jan Beulich 2019-04-29 7:07 ` [Xen-devel] " Jan Beulich
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5CC2CB8C02000078002295AA@prv1-mh.provo.novell.com \ --to=jbeulich@suse.com \ --cc=206497@studenti.unimore.it \ --cc=andrew.cooper3@citrix.com \ --cc=julien.grall@arm.com \ --cc=nd@arm.com \ --cc=sstabellini@kernel.org \ --cc=stefanos@xilinx.com \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.