|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH V3 1/2] x86/altp2m: Add hypercall to set a range of sve bits
On 12.12.2019 13:26, George Dunlap wrote: > On 12/12/19 9:37 AM, Alexandru Stefan ISAILA wrote: >> >> >> On 06.12.2019 17:29, George Dunlap wrote: >>> On 11/21/19 3:02 PM, Alexandru Stefan ISAILA wrote: >>>> By default the sve bits are not set. >>>> This patch adds a new hypercall, xc_altp2m_set_supress_ve_multi(), >>>> to set a range of sve bits. >>>> The core function, p2m_set_suppress_ve_multi(), does not brake in case >>>> of a error and it is doing a best effort for setting the bits in the >>>> given range. A check for continuation is made in order to have >>>> preemption on big ranges. >>>> >>>> Signed-off-by: Alexandru Isaila <aisaila@xxxxxxxxxxxxxxx> >>> >>> There's something strangely deformed in your mail that makes it hard for >>> me to apply the patches to my tree, and I'm not sure why. >>> >>> It seems the core mail is base64-encrypted; and that *inside* that >>> base64 encryption is a bunch of Windows-style linefeeds. The result is >>> that when I try to download your series and apply it with git-am, I get >>> loads of rejected hunks with "^M" at the end of them. >>> >>> Sometimes I've been able to work around this by going on patchew.org/Xen >>> and getting an mbox from there; but it doesn't seem to have your series >>> (perhaps because it doesn't have a cover letter). >>> >>> Looking at the headers, it seems this is coming from git itself. Do you >>> perhaps have "transferEncoding" set to "base64"? If so, chance you >>> could try setting it to 'auto', and setting 'assume8bitEncoding = true"? >> >> I didn't have anything set for transferEncoding in .gitconfig but I can set >> assume8bitEncoding = yes >> transferEncoding = 8bit >> >> for the future. >> >> Sorry for the inconvenience. > > Well, I'm also sorry that I'm having trouble on my end. :-) You'd > think that you doing "git send-email" and me doing "git am" would Just > Work(tm), and it's frustrating that it doesn't. *Hopefully* those > changes will make it work; otherwise we'll have to figure out something > else. > We have to solve this somehow so on the next ver. please let me know if everything is ok. Alex _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |