The error message is wrong (given AMD's older interpretation of what a NUL
segment should contain, attribute wise), and actively unhelpful because you
only get it in response to a hypercall where the one piece of information you
cannot provide is the segment selector.
Fix the message to talk about segment attributes, rather than the selector.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
{
if ( seg != x86_seg_ds && seg != x86_seg_es )
{
- gprintk(XENLOG_ERR, "Null selector provided for CS, SS or TR\n");
+ gprintk(XENLOG_ERR, "Null segment attributes for CS, SS or TR\n");
return -EINVAL;
}
return 0;