Hi Jan,
On 06/05/2022 14:46, Jan Beulich wrote:
On 06.05.2022 15:43, Julien Grall wrote:
You say future, has this option been merged or still in discussion on
the ML?
"future" as in "no released version yet". The change is present on the
binutils master branch.
Thanks for the clarification.
On 06/05/2022 15:18, Andrew Cooper wrote:
> On 06/05/2022 14:46, Jan Beulich wrote:
>> On 06.05.2022 15:43, Julien Grall wrote:
>>> You say future, has this option been merged or still in discussion on
>>> the ML?
>> "future" as in "no released version yet". The change is present on the
>> binutil
On 06/05/2022 14:46, Jan Beulich wrote:
> On 06.05.2022 15:43, Julien Grall wrote:
>> You say future, has this option been merged or still in discussion on
>> the ML?
> "future" as in "no released version yet". The change is present on the
> binutils master branch.
In which case, I'd recommend sa
On 06.05.2022 15:43, Julien Grall wrote:
> You say future, has this option been merged or still in discussion on
> the ML?
"future" as in "no released version yet". The change is present on the
binutils master branch.
> On 06/05/2022 14:37, Jan Beulich wrote:
>> We cannot really avoid such and w
Hi,
You say future, has this option been merged or still in discussion on
the ML?
On 06/05/2022 14:37, Jan Beulich wrote:
We cannot really avoid such and we're also not really at risk because of
them, as we control page table permissions ourselves rather than relying
on a loader of some sort.
We cannot really avoid such and we're also not really at risk because of
them, as we control page table permissions ourselves rather than relying
on a loader of some sort.
Signed-off-by: Jan Beulich
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -397,6 +397,8 @@ endif
AFLAGS += -D__ASSEMBLY__
+LD
